SimbaApacheCassandraODBC …cdn.simba.com/products/Cassandra/doc/Simba_Cassandra_ODBC_Qu… · PowerBI.Ifyouareusingthe32-bitversionofPowerBI,thenyouneedtousethe 32-bitversionofthedriver.Ifyouareusingthe64-bitversionofPowerBI,then

Simba Apache Cassandra ODBCDriver with SQL Connector

Quickstart Guide for Windows

Simba Technologies Inc.

September 15, 2015

Copyright © 2015 Simba Technologies Inc. All Rights Reserved.

Information in this document is subject to change without notice. Companies, names anddata used in examples herein are fictitious unless otherwise noted. No part of thispublication, or the software it describes, may be reproduced, transmitted, transcribed,stored in a retrieval system, decompiled, disassembled, reverse-engineered, or translatedinto any language in any form by any means for any purpose without the express writtenpermission of Simba Technologies Inc.

Trademarks

Simba, the Simba logo, SimbaEngine, SimbaEngine C/S, SimbaExpress and SimbaLibare registered trademarks of Simba Technologies Inc. All other trademarks and/orservicemarks are the property of their respective owners.

Contact Us

Simba Technologies Inc.938 West 8th AvenueVancouver, BC CanadaV5Z 1E5

Tel: +1 (604) 633-0008

Fax: +1 (604) 633-0004

www.simba.com

www.simba.com 2

Simba Apache Cassandra ODBC Driverwith SQL Connector Quickstart Guide for Windows

http://www.simba.com/

About This Guide

Purpose

The Simba Apache Cassandra ODBC Driver with SQL Connector Quickstart Guide forWindows is targeted towards users of the Simba Apache Cassandra ODBC Driver withSQL Connector, showing you how to set up your environment quickly so that you canevaluate and use the driver.

Audience

The guide is intended for end users of the Simba Apache Cassandra ODBC Driver withSQL Connector who want to evaluate the driver by using it in an application.

Knowledge Prerequisites

To use the Simba Apache Cassandra ODBC Driver with SQL Connector, the followingknowledge is helpful:

l Familiarity with the platform on which you are using the Simba Apache CassandraODBC Driver with SQL Connector

l Ability to use the data source to which the Simba Apache Cassandra ODBC Driverwith SQL Connector is connecting

l An understanding of the role of ODBC technologies and driver managers in con-necting to a data source

l Experience creating and configuring ODBC connectionsl Exposure to SQL

Document Conventions

Italics are used when referring to book and document titles.

Bold is used in procedures for graphical user interface elements that a user clicks and textthat a user types.

Monospace font indicates commands, source code or contents of text files.

Underline is not used.

The pencil icon indicates a short note appended to a paragraph.

The star icon indicates an important comment related to the preceding paragraph.

The thumbs up icon indicates a practical tip or suggestion.

www.simba.com 3


Table of Contents

Installing and Running Cassandra 5

Importing Sample Data into Cassandra 6

Installing the Driver 7

Configuring the Driver 8

Connecting to the Data Source 9Using Microsoft Excel 9Using Microsoft Access 12Using Tableau 13Using a Linked Server 14Using Power BI 17Using Qlik Sense 18Using Qlikview 18Using SPSS Statistics 20

Contact Us 21

Appendix A Troubleshooting 22Architecture Mismatch Problems 22Known Issues when using Linked Server 23

Appendix B Third Party Trademarks and Licenses 25

www.simba.com 4


Installing and Running Cassandra

You can download Cassandra from http://planetcassandra.org/cassandra/.

Cassandra installation guides are available athttp://www.datastax.com/documentation/cassandra/2.0/cassandra/gettingStartedCassandraIntro.html.

The Simba Apache Cassandra ODBC Driver with SQL Connector supportsCassandra 2.0 or later. Ensure that you download an appropriate version ofCassandra

To start Cassandra:1. Open a command prompt window:

l If you are using Windows 7 or earlier, click the Start button , then click AllPrograms, then click Accessories, and then click Command Prompt.

l Or, if you are using Windows 8 or later, click the arrow button at the bottom ofthe Start screen, then find the Windows System program group, and then clickCommand Prompt.

2. In the command prompt window, browse to the \bin subfolder of your Cassandrainstallation, and then run the following command:cassandra –f

If the command runs correctly, then many lines of diagnostic information appear inthe window. The following line appears near the end, where PortNumber is the porton which Cassandra is listening on all interfaces for CQL client requests:Starting listening for CQL client on/0.0.0.0:PortNumber...

The following text appears as one of the last lines in the Command Prompt window:Listening for thrift clients...

3. To verify that connectivity to Cassandra is working correctly, open a new CommandPrompt window, then browse to the \bin subfolder of your Cassandra installation,and then start the Cassandra shell by running the following command:cqlsh

If Cassandra is working correctly, then a connection to your local Cassandrainstance is established and the cqlsh> prompt appears as the last line in theCommand Prompt window.

www.simba.com 5


http://planetcassandra.org/cassandra/

http://www.datastax.com/documentation/cassandra/2.0/cassandra/gettingStartedCassandraIntro.html

http://www.datastax.com/documentation/cassandra/2.0/cassandra/gettingStartedCassandraIntro.html

Importing Sample Data into Cassandra

The following procedure describes how to import some sample data if you do not alreadyhave data to use.

To import sample data into Cassandra:1. Download the sample data set available at http://www.simba.com/wp-

content/uploads/2015/01/FAA_Cassandra.zip.The sample data set is a modified version of the FAA data set. The originalFAA data set is available for download at http://www.transtats.bts.gov/DL_SelectFields.asp?Table_ID=236&DB_Short_Name=On-Time.

2. Create a new folder in a convenient location, and then extract the sample data setinto the folder.

3. If you have not already done so, start Cassandra and connect to your localCassandra instance by following the procedure in Installing and Running Cassandraon page 5.

4. To create the keyspace for a new column family, run the following command:create keyspace faa WITH REPLICATION = { 'class' :'SimpleStrategy', 'replication_factor' : 1 };

5. To switch to the keyspace you created in step 4, run the following command:use faa;

6. To create a column family for your data, run the following command:CREATE COLUMNFAMILY airline ("key" int PRIMARY KEY,"UNIQUE_CARRIER" varchar, "AIRLINE_ID" varchar,"CARRIER" varchar, "TAIL_NUM" varchar, "FL_NUM"varchar);

7. Exit the Cassandra shell by using the quit or exit command, then navigate to thedirectory where you extracted the sample data set in step 2, and then start theCassandra shell again by running the cqlsh command.

8. To import data from the Airline.csv file into the column family that you created instep 6, run the following command:COPY faa.airline (key, "UNIQUE_CARRIER", "AIRLINE_ID","CARRIER", "TAIL_NUM", "FL_NUM") FROM 'Airline.csv' WITHHEADER=true;

9. To verify that the data was imported correctly, run the following command:select * from faa.airline;

The imported data appears in the Command Prompt window.

www.simba.com 6


http://www.simba.com/wp-content/uploads/2015/01/FAA_Cassandra.zip

http://www.simba.com/wp-content/uploads/2015/01/FAA_Cassandra.zip

http://www.transtats.bts.gov/DL_SelectFields.asp?Table_ID=236&DB_Short_Name=On-Time

http://www.transtats.bts.gov/DL_SelectFields.asp?Table_ID=236&DB_Short_Name=On-Time

Installing the Driver

The Simba Apache Cassandra ODBC Driver with SQL Connector is available fordownload from http://www.simba.com/connectors/apache-cassandra-odbc.

On 64-bit Windows operating systems, you can execute 32- and 64-bit applicationstransparently. You must use the version of the driver matching the bitness of the clientapplication accessing data in Cassandra:

l SimbaCassandraODBC32.msi for 32-bit applicationsl SimbaCassandraODBC64.msi for 64-bit applications

You can install both versions of the driver on the same computer.

For an explanation of how to use ODBC on 64-bit editions of Windows, seehttp://www.simba.com/wp-content/uploads/2010/10/HOW-TO-32-bit-vs-64-bit-ODBC-Data-Source-Administrator.pdf.

To install the Simba Apache Cassandra ODBC Driver with SQL Connector:1. Depending on the bitness of your client application, double-click to run

SimbaCassandraODBC32.msi or SimbaCassandraODBC64.msi.2. Click Next.3. Select the check box to accept the terms of the License Agreement if you agree, and

then click Next.4. To change the installation location, click Change, then browse to the desired folder,

and then click OK. To accept the installation location, click Next.5. Click Install.6. When the installation completes, click Finish.7. If you received a license file via e-mail, then copy the license file into the \lib

subfolder in the installation folder you selected in step 4.To avoid security issues, you may need to save the license file on your localcomputer prior to copying the file into the \lib subfolder.

www.simba.com 7


http://www.simba.com/connectors/apache-cassandra-odbc

http://www.simba.com/wp-content/uploads/2010/10/HOW-TO-32-bit-vs-64-bit-ODBC-Data-Source-Administrator.pdf

http://www.simba.com/wp-content/uploads/2010/10/HOW-TO-32-bit-vs-64-bit-ODBC-Data-Source-Administrator.pdf

Configuring the Driver

To use the Simba Apache Cassandra ODBC Driver with SQL Connector, you need toconfigure a Data Source Name (DSN) to connect to your data source using a clientapplication, such as Microsoft Excel or Tableau.

To create a Data Source Name:1. Open the ODBC Administrator:

l If you are using Windows 7 or earlier, click the Start button , then click AllPrograms, then click the Simba Cassandra ODBC Driver program groupcorresponding to the bitness of the client application accessing data in Cas-sandra, and then click ODBC Administrator.

l Or, if you are using Windows 8 or later, on the Start screen, typeODBCadministrator, and then click the ODBC Administrator search result cor-responding to the bitness of the client application accessing data in Cas-sandra.

2. Click the System DSN tab.3. Select Sample Simba Cassandra DSN in the list of DSNs, and then click

Configure.4. In the Host field, type the IP address or host name of your Cassandra server.

If you are running Cassandra on your local computer, then type localhost inthe Host field.

5. In the Port field, type the number of the port that the Cassandra server uses to listenfor client requests.

By default, Cassandra uses port 9042.

6. If your Cassandra data source is configured to use authentication, then select UserName and Password in the Authentication Type list and then type yourcredentials in the User and Password fields.

7. To test the connection to your Cassandra data source, ensure that Cassandra isrunning, and then click Test in the Simba Cassandra ODBC Driver DSN Setupdialog box. If you are prompted for authentication, type your user name andpassword for accessing the Cassandra instance, and then click OK

The Test Results dialog box appears, displaying a message informing you whetherthe connection succeeded or failed.

8. Click OK to close the Test Results dialog box, and then click OK to save your DSNand close the Simba Cassandra ODBC Driver DSN Setup dialog box.

For more information about configuring the Simba Apache Cassandra ODBCDriver with SQL Connector, see the Simba Apache Cassandra ODBC Driver withSQL Connector Installation and Configuration Guide.

www.simba.com 8


Connecting to the Data Source

After creating a Data Source Name for connecting to your Cassandra data source, you canconnect to the data source using a client application. The following are a few examples ofthe applications that you can use to access your data:

l Using Microsoft Excel on page 9l Using Microsoft Access on page 12l Using Tableau on page 13l Using a Linked Server on page 14l Using Power BI on page 17l Using Qlik Sense on page 18l Using Qlikview on page 18l Using SPSS Statistics on page 20

Using Microsoft Excel

In Microsoft Excel, you can connect to Cassandra data by using one of the following tools:l Data Connection Wizard—Use this wizard to retrieve a table from Cassandra.When using this wizard, you can only retrieve a single table at a time, and you cannotfilter the result set.

l Query Wizard—Use this wizard from Microsoft Query to define and run a simplequery. You can query multiple tables and columns, and sort and filter the result set.

l Microsoft Query—Work directly in the application to define and run complex quer-ies. For example, you can define parameterized queries and different types of joins.

The following procedures are written for Microsoft Excel 2013. The Simba ApacheCassandra ODBC Driver with SQL Connector also supports Excel 2010.

Using the Data ConnectionWizard

To connect using the Data Connection Wizard:1. In Excel, select the Data tab in the ribbon, then click From Other Sources in the

Get External Data group, and then click From Data Connection Wizard.2. In the Data Connection Wizard, select ODBC DSN in the list of data source types,

and then click Next.3. In the list of ODBC data sources, select Sample Simba Cassandra DSN, and then

click Next.

www.simba.com 9


If the connection fails, confirm that the bitness of the driver that you areusing matches the bitness of Excel. If you are using the 32-bit version ofExcel, then you need to use the 32-bit version of the driver. If you are usingthe 64-bit version of Excel, then you need to use the 64-bit version of thedriver. For more information about diagnosing the issue, see ArchitectureMismatch Problems on page 22.

4. From the list of tables, select the name of a table that you want to retrieve, and thenclick Finish.

5. In the Import Data dialog box, in the Existing Worksheet field, specify the cellwhere you want the top left corner of the selected table to be inserted, and then clickOK.

Data from the selected table is displayed in the current Excel worksheet.

Using the Query Wizard

The Query Wizard is part of Microsoft Query. When the Query Wizard is open, youcan switch from using the Query Wizard to working directly in Microsoft Query atany time by clicking Cancel and then clicking Yes at the prompt.

To connect using the Query Wizard:1. In Excel, select the Data tab in the ribbon, then click From Other Sources in the

Get External Data group, and then click From Microsoft Query.2. In the Choose Data Source dialog box, on the Databases tab, select Sample

Simba Cassandra DSN.3. Make sure that the Use the Query Wizard to create/edit queries check box is

selected, and then click OK.If the connection fails, confirm that the bitness of the driver that you areusing matches the bitness of Excel. If you are using the 32-bit version ofExcel, then you need to use the 32-bit version of the driver. If you are usingthe 64-bit version of Excel, then you need to use the 64-bit version of thedriver. For more information about diagnosing the issue, see ArchitectureMismatch Problems on page 22.

4. In the Query Wizard, select the tables or columns that you want to include in yourquery by selecting each item in the left pane and then clicking the > button. Whenyour selection is complete, click Next.

If the tables or columns that you want to include are not listed in the leftpane, then click Options and configure the table options as needed.

5. To filter the data in your query, select a column from the left pane, then select acomparison operator from the list, and then specify a value in the list on the right.Repeat as needed to define additional filters, and then click Next to proceed.

6. To sort the data in your query, select the column on which you want to base thesorting and then specify whether to sort the data in ascending or descending order.Repeat as needed to define additional levels of sorting, and then click Next toproceed.

www.simba.com 10


7. Optionally, to save the query so that you can run it again without going through theprocess of recreating it, click Save Query, type a unique name for the query, andthen click Save

8. Select Return Data To Microsoft Excel and then click Finish9. In the Import Data dialog box, in the Existing Worksheet field, specify the cell where

you want the first column header of the result set to appear, and then click OK.

Data retrieved from the defined query is displayed in the current Excel spreadsheet.

UsingMicrosoft Query

To connect by working directly in Microsoft Query:1. In Excel, select the Data tab in the ribbon, then click From Other Sources in the

Get External Data group, and then click From Microsoft Query.2. In the Choose Data Source dialog box, on the Databases tab, select Sample

Simba Cassandra DSN.3. Clear the Use the Query Wizard to create/edit queries check box, and then click

OK4. In the Add Tables dialog box, select the tables that you want to include in your query

by selecting each table and then clicking Add. When your selection is complete, clickClose. If necessary, you can reopen the dialog box to add more tables by clicking

Add Table(s)If the tables that you want to include are not listed in the dialog box, thenclick Options and configure the table options as needed.

5. To define joins between your tables, in the upper pane, click and drag a field fromone table to a field in another table. You can then double-click the line between thefields to modify the join.

For detailed information about defining joins in Microsoft Query, see thesection titled Creating, Changing, and Removing Joins in the MicrosoftQuery Help documentation that is provided in the application.

6. Select the columns that you want to include in your query by double-clicking thecolumn names from the tables. You can double-click the asterisk (*) to select all thecolumns from a table.

If Auto Query is enabled, then the results of your query automaticallyappear in the lower pane. Otherwise, you must click Query Now to runthe query and see the results.

7. To filter the data in your query, click Show/Hide Criteria and then use theoptions in the criteria pane to define your filters.

8. To sort the data in your query, select a column header in the lower pane and then

click Sort Ascending or Sort Descending as needed.

9. If Auto Query is disabled, then click Query Now to run your query and seethe results.

www.simba.com 11


10.When you are finished defining your query, click Return Data to retrieve theresult set in Excel.

11. In the Import Data dialog box, in the Existing Worksheet field, specify the cell whereyou want the first column header of the result set to appear, and then click OK.

Data retrieved from the defined query appears in the current Excel spreadsheet.

For more information about defining complex queries using Microsoft Query, seethe Microsoft Query Help documentation that is provided in the application.

Using Microsoft Access

You can connect to Cassandra data by importing it into a Microsoft Access database or bycreating a table that links to the Cassandra data.

The following procedures are written for Microsoft Access 2013. The Simba ApacheCassandra ODBC Driver with SQL Connector also supports Access 2010.

ImportingData

To import Cassandra data:1. In Access, select the External Data tab in the ribbon and then click

ODBC Database.2. Select Import the source data into a new table in the current database and

then click OK.3. In the Select Data Source dialog box, select the Machine Data Source tab, then

select Sample Simba Cassandra DSN from the list, and then click OK.If the connection fails, confirm that the bitness of the driver that you areusing matches the bitness of Access. If you are using the 32-bit version ofAccess, then you need to use the 32-bit version of the driver. If you areusing the 64-bit version of Access, then you need to use the 64-bit version ofthe driver. For more information about diagnosing the issue, seeArchitecture Mismatch Problems on page 22.

4. In the Import Objects dialog box, select the tables that you want to import, and thenclick OK.

5. In the Get External Data dialog box, select the Save import steps check box if youwant to save the import process so that you can run it again at a later time, and thenclick Close.

The tables that you selected appear in the Navigation Pane on the left.

Linking to Data

To link to Cassandra data:1. In Access, select the External Data tab in the ribbon and then click

ODBC Database.

www.simba.com 12


2. Select Link to the data source by creating a linked table and then click OK.3. In the Select Data Source dialog box, select the Machine Data Source tab, then

select Sample Simba Cassandra DSN from the list, and then click OK.If the connection fails, confirm that the bitness of the driver that you areusing matches the bitness of Access. If you are using the 32-bit version ofAccess, then you need to use the 32-bit version of the driver. If you areusing the 64-bit version of Access, then you need to use the 64-bit version ofthe driver. For more information about diagnosing the issue, seeArchitecture Mismatch Problems on page 22.

4. In the Link Tables dialog box, select the tables that you want to link to, and then clickOK.

5. If the Select Unique Record Identifier dialog box opens, select the column thatcontains the unique identifiers for the rows in the table (for example, the primary keycolumn) and then click OK. You may be prompted to do this for multiple tables.

Access creates a linked table in the Navigation Pane for each Cassandra table that youselected.

Using Tableau

The following procedure is written for Tableau 8. The Simba Apache Cassandra ODBCDriver with SQL Connector also supports Tableau 7.

To connect to your Cassandra data source using Tableau:1. In Tableau, click Connect to Data in the left navigation pane, and then selectOther

Databases (ODBC) from the bottom of the pane.2. In the DSN list, select Sample Simba Cassandra DSN and then click Connect.

If the connection fails, confirm that the bitness of the driver that you areusing matches the bitness of Tableau. If you are using the 32-bit version ofTableau, then you need to use the 32-bit version of the driver. If you areusing the 64-bit version of Tableau, then you need to use the 64-bit versionof the driver. For more information about diagnosing the issue, seeArchitecture Mismatch Problems on page 22.

3. Select the Single Table option and then click the magnifying glass to open theSelect Table dialog box.

4. Select the name of a table that you want to retrieve, and then click Select.If the database contains a large number of tables, you may need to clickLoad to see the list of tables.

5. To load the selected table, click OK.

www.simba.com 13


If the following warning is displayed, click OK:

This warning is displayed because Tableau sees only a generic driver and attemptsto determine the capabilities of the driver. The warning does not affect how the driverwill operate in Tableau.

6. In the Data Connection dialog box, click Connect live so that Tableau does notimport all of the data and you work on the data in Cassandra.

Data retrieved from the selected table is loaded in Tableau, with the columns listed asdimensions or measures depending on the data type. You can now create reports on thetable.

Using a Linked Server

A linked server enables you to execute distributed queries against tables stored in aMicrosoft SQL Server instance and another data source. Use the Microsoft SQL ServerManagement Studio to link your Cassandra data source to a SQL Server instance andthen execute distributed queries against both data sources.

You can use either of the following methods to create the linked server:l To create the linked server by using the options in the Object Explorer, see Creatinga Linked Server using the Object Explorer on page 14.

l To create the linked server by executing stored procedures, see Creating a LinkedServer using Stored Procedures on page 15.

Creating a Linked Server using the Object Explorer

You can use the options available in the user interface of the Management Studio to createyour linked server.

To create a linked server using the Object Explorer:1. In Management Studio, connect to your Database Engine instance.2. In the Object Explorer, expand Server Objects, then right-click Linked Servers,

and then click New Linked Server.3. In the New Linked Server dialog box, use the options on the General page to

configure your linked server:

www.simba.com 14


a) In the Linked Server field, type a name for your linked server.b) Under Server Type, select Other data source.c) In the Provider list, selectMicrosoft OLE DB Provider for ODBC Drivers.d) In the Data Source field, type Sample Simba Cassandra DSN.

4. If your Cassandra data source requires a user name and password forauthentication, then use the options in the Security page to provide your credentials:

a) Select Be made using this security context.b) In the Remote Login field, type your user name for accessing the data

source.c) In theWith Password field, type the password corresponding to the user

name you typed in step b.5. Click OK to save your settings and link the Cassandra data source to the SQL Server

instance.If the connection fails, confirm that the bitness of the driver that you areusing matches the bitness of the SQL Server instance that you are using tocreate the server link. For example, if you are creating the server link from a32-bit SQL Server instance, then you need to use the 32-bit version of thedriver. Contact your SQL Server administrator as needed to confirm thebitness of the server.

The linked server is displayed as a node under the Linked Servers branch in the ObjectExplorer, and you can expand the node to browse the contents of the server down to thetable level. You can now start executing distributed queries to work with data from theCassandra data source and the SQL Server instance. For information about executingqueries against the linked server, see Querying a Linked Server on page 16.

Creating a Linked Server using Stored Procedures

As an alternative to using the options in the user interface, you can execute storedprocedures in Management Studio to create your linked server.

To create a linked server using stored procedures:1. In Management Studio, connect to your Database Engine instance.2. In the toolbar at the top of Management Studio, click New Query.3. In the editor window that appears, type the following statement for creating the

linked server, where LinkedServerName is the name of the linked server:EXEC master.dbo.sp_addlinkedserver@server=N'LinkedServerName', @srvproduct=N'CASSANDRA',@provider=N'MSDASQL', @datasrc=N'Sample Simba CassandraDSN'

4. If your Cassandra data source requires a user name and password forauthentication, then type the following statement, where LinkedServerName is thename of the linked server and UserName and Password are your credentials:EXEC master.dbo.sp_addlinkedsrvlogin

www.simba.com 15


@rmtsrvname=N'LinkedServerName', @useself=N'False',@locallogin=NULL, @rmtuser=N'UserName',@rmtpassword=N'Password'

5. In the toolbar at the top, click Execute.The Messages pane appears and displays a message indicating whether thestatements were executed successfully.

If the connection fails, confirm that the bitness of the driver that you areusing matches the bitness of the SQL Server instance that you are using tocreate the server link. For example, if you are creating the server link from a32-bit SQL Server instance, then you need to use the 32-bit version of thedriver. Contact your SQL Server administrator as needed to confirm thebitness of the server.

6. In the Object Explorer, select Linked Servers and then click Refresh .

The linked server appears as a node under the Linked Servers branch in the ObjectExplorer, and you can expand the node to browse the contents of the server down to thetable level. You can now start executing distributed queries to work with the data from theCassandra data source and the SQL Server instance. For information about executingqueries against the linked server, see Querying a Linked Server on page 16.

For information about the sp_addlinkedserver stored procedure, see the sp_addlinkedserver (Transact-SQL) article in the Transact-SQL Reference availableat https://msdn.microsoft.com/en-CA/library/ms190479.aspx.

For information about the sp_addlinkedsrvlogin stored procedure, see the sp_addlinkedsrvlogin (Transact-SQL) article in the Transact-SQL Reference availableat https://msdn.microsoft.com/en-CA/library/ms189811.aspx.

Querying a Linked Server

Normally, you can query data by using scripts in Management Studio; however, scripts arenot supported for linked servers. To execute queries against a linked server, use theeditor.

To query a linked server:1. In the toolbar at the top of Management Studio, click New Query.2. In the editor window that appears, type your query.3. In the toolbar at the top, click Execute.

Data retrieved from your query is displayed in the Results pane.

For information about known issues that you might encounter while querying alinked server, see Known Issues when using Linked Server on page 23.

www.simba.com 16


https://msdn.microsoft.com/en-CA/library/ms190479.aspx


Using Power BI

You can import Cassandra data into Power BI Desktop through the PowerBI ODBC connector. You use a DSN connection string to connect Power BI to thedatabase. For more information about creating connection strings for the Simba ApacheCassandra ODBC Driver with SQL Connector, see the Simba Apache Cassandra ODBCDriver with SQL Connector Installation and Configuration Guide.

Make sure that the bitness of the driver that you are using matches the bitness ofPower BI. If you are using the 32-bit version of Power BI, then you need to use the32-bit version of the driver. If you are using the 64-bit version of Power BI, thenyou need to use the 64-bit version of the driver. For more information aboutdiagnosing the issue, see Architecture Mismatch Problems on page 22.

To retrieve data from your Cassandra data store using Power BI:1. In Power BI Desktop, click Get Data > More.2. In the Get Data dialog box, from the list of data sources, select ODBC and click

Connect.3. In the From ODBC dialog box, in the Connection String field, type:

DSN=Sample Simba Cassandra DSN

4. Optionally, to specify what data is returned with a SQL statement, click SQLStatement (optional) and, in the field that is displayed, type or paste aSQL statement to specify the data.

5. Click OK. In the ODBC Driver dialog box, choose one:l If your data store requires credentials for access, then in the Usernameand Password fields, type your credentials for accessing your data store, andthen click Connect.

l Otherwise, from the column on the left, select Default or Custom and clickConnect.

6. The Navigator opens, with a list of the schemas and tables that are contained in thedata store.

If you used a SQL statement to specify what data is returned, then only thetables containing the specified data are displayed.

7. In the Navigator, select the check boxes next to the tables that you want to import,and click Load.

The selected tables are loaded into Power BI Desktop, and are listed in the Fields taskpane. You can now use Power BI to analyze the data in those tables.

For more information about connecting to a database in Power BI Desktop, seethe Power BI Help documentation that is linked from the application.

For more Power BI tutorials and how-to information, seehttp://www.simba.com/topic/power-bi.

www.simba.com 17


http://www.simba.com/topic/power-bi

Using Qlik Sense

You can import Cassandra data into a Qlik Sense app through an ODBC connection. Youspecify which tables and columns in your data store to load into Qlik Sense, and thenconstruct charts and stories to analyze and present that data.

Make sure that the bitness of the driver that you are using matches the bitness ofQlik Sense Desktop. If you are using the 32-bit version of Qlik Sense Desktop,then you need to use the 32-bit version of the driver. If you are using the 64-bitversion of Qlik Sense Desktop, then you need to use the 64-bit version of thedriver. For more information about diagnosing the issue, see ArchitectureMismatch Problems on page 22.

To retrieve data from your Cassandra data store using Qlik Sense:1. In Qlik Sense Desktop, from the Qlik Sense Desktop Hub, click Create New App.2. In the Create New App dialog box, type the name of your new app and click Create,

then click Open App.3. In the new app, click Add Data.4. In the Select a Data Source dialog box, make sure Connect My Data is selected,

and then click ODBC.5. In the Create New Connection (ODBC) dialog box, make sure System DSN and the

correct bitness for your version of Qlik Sense Desktop are selected.6. From the list of data sources, select Sample Simba Cassandra DSN .7. If your data store requires credentials for access, then in the Username

and Password fields, type your credentials for accessing your data store.8. Click >.9. In the Select Data dialog box, from the list of tables, select the check box next to

each table that you want to include in your app.10.To specify which columns from each table to include in your app, select the table,

and then select the columns to include.11.When you are done selecting the tables and columns that you need, click Load and

Finish. The Select Data dialog box closes and the Data Loading dialog box opens.12.When the data has finished loading, click Edit the Sheet.

You can now use Qlik Sense to analyze the data in those tables.

For more information about connecting to a database in Qlik Sense, see the QlikSense documentation that is available at http://www.qlik.com/support/.

Using Qlikview

You can import Cassandra data into Qlikview through an ODBC connection. Qlikview'sScript Editor generates a SQL script that connects to your data source and imports yourdata, so that you can analyze the data in Qlikview.

www.simba.com 18


http://www.qlik.com/support/

Make sure that the bitness of the driver that you are using matches the bitness ofQlikview. If you are using the 32-bit version of Qlikview, then you need to use the32-bit version of the driver. If you are using the 64-bit version of Qlikview, then youneed to either use the 64-bit version of the driver, or, in the Edit Script dialog box,select the Force 32 Bit check box. For more information about diagnosing theissue, see Architecture Mismatch Problems on page 22.

To retrieve data from your Cassandra data store using Qlikview:1. In Qlikview, click File > New. If the Getting Started Wizard opens, close it. A new

empty document is displayed in Qlikview.2. Select File > Edit Script.3. In the Edit Script dialog box, in the Database drop-down list, make sureODBC is

selected, and click Connect.4. In the Connect to Data Source dialog box, from the Data Sources list, select

Sample Simba Cassandra DSN .5. If your data store requires credentials for access, then in the User ID and Password

fields, type your credentials for accessing your data store.6. To make sure your connection is working, click Test Connection and note the

results in the Connection Test dialog box.7. Click OK. The Connect to Data Source dialog box closes and an

ODBC CONNECT statement is displayed in the main script area of the Edit Scriptdialog box.

8. Click Select.9. In the Create Select Statement dialog box, from the Database Tables list, select a

table that contains data that you want to analyze in Qlikview.10.From the Fields list, select the fields that contain data that you want to analyze in

Qlikview.11.To select data from another table, click Add and select the table and its fields,

selecting a different table from the Database Tables list.12.When you are done selecting the data to include in your app, click OK. The Create

Select Statement dialog box closes.13.Select File > Save Entire Document. Browse to the location where you want to

save the script, specify a file name for the script, and click Save.14.Click OK. The Edit Script dialog box closes.15.Select File > Reload.

The script is executed and the specified tables are loaded into Qlikview. You can now useQlikview to analyze the data in those tables.

For more information about connecting to a database in Qlikview, see the QlikviewHelp documentation that is linked from the application.

www.simba.com 19


Using SPSS Statistics

You can import Cassandra data into SPSS Statistics with a standard SQL query. TheSPSS Database Wizard can automatically generate and execute an appropriate querybased on parameters you specify.

The following procedure is written for SPSS Statistics 23. The Simba Apache CassandraODBC Driver with SQL Connector also supports earlier versions of SPSS.

Make sure that the bitness of the driver that you are using matches the bitness ofSPSS. If you are using the 32-bit version of SPSS, then you need to use the 32-bitversion of the driver. If you are using the 64-bit version of SPSS, then you need touse the 64-bit version of the driver. For more information about diagnosing theissue, see Architecture Mismatch Problems on page 22.

To retrieve data from your Cassandra data source using SPSS:1. In SPSS Statistics, select File > Database > New Query. The Database Wizard

opens at theWelcome page.2. From the ODBC Data Source list, select Sample Simba Cassandra DSN.3. Under Select the table types, select the check boxes corresponding to the types of

tables you want to retrieve and then click Next.4. On the Select Data page, select and order the tables and fields that you want to

retrieve and then click Next.5. If you selected more than one table, then on the Specify Relationships page, specify

how the tables should be joined and then click Next.6. On the Limit Retrieved Cases page, specify how to limit the data you retrieve and

then click Next.7. On the Define Variables page, specify how SPSS should define those variables and

then click Next.8. On the Results page, review the generated SQL.9. Make sure that Retrieve the data I have selected is selected and then click

Finish.

Data retrieved from the selected tables is displayed in SPSS Statistics in a new Datasetwindow. You can now use SPSS Statistics to analyze the data.

For more information about connecting to a database in SPSS Statistics, see theSPSS Statistics Help documentation that is provided in the application.

www.simba.com 20


Contact Us

If you have difficulty using the driver, please contact our Technical Support staff. Wewelcome your questions, comments, and feature requests.

Technical Support is available Monday to Friday from 8 a.m. to 6 p.m. Pacific Time.

To help us assist you, prior to contacting Technical Support please prepare adetailed summary of the client and server environment including operating systemversion, patch level, and configuration.

You can contact Technical Support via:l E-mail—[email protected] Web site—www.simba.coml Telephone—(604) 633-0008 Extension 3l Fax—(604) 633-0004

You can also follow us on Twitter @SimbaTech

www.simba.com 21


mailto:[email protected]?subject=Technical Support

http://www.simba.com/

Appendix A Troubleshooting

Architecture Mismatch Problems

If you encounter an error message similar to "The specified DSN contains an architecturemismatch between the Driver and Application", then the bitness of the application you areusing to attempt to connect to the Cassandra data source does not match the bitness ofthe driver that you are using. You may be attempting to connect a 32-bit application to a64-bit driver, or vice versa. Ensure that the bitness of your application matches the bitnessof driver that you are trying to use.

Applications in Microsoft Office 2007 and earlier are 32-bit only.

To determine the bitness of an application:1. Open the About dialog box for the application. For example, to open the About dialog

box for Microsoft Office 2013 products, click the File tab in the ribbon, then clickAccount in the left pane, and then click the About Application button (whereApplication is the application name).

2. In the About dialog box, look for the words 32-bit or 64-bit:l If the About dialog box contains 32-bit then you must use a 32-bit driver to con-nect to that application.

l If the About dialog box contains 64-bit then you must use a 64-bit driver to con-nect to that application.

For example, the following image shows the About dialog box for a 32-bit version ofMicrosoft Excel 2013.

www.simba.com 22


Known Issues when using Linked Server

The following are known issues that you may encounter when using a linked server to workwith your data.

Scripting Options Return Errors

When using a linked server, the scripting options that are accessible from the ObjectExplorer are not supported. For example, if you try to execute a query using one of theScript Table as options, the Management Studio will return an error message stating thatthe specified table "contains no columns that can be selected or the current user does nothave permissions on that object".

As a workaround for this issue, define your queries using the editor that opens when youclick the New Query button in the toolbar instead of using the scripting options.

www.simba.com 23


Type Conversion Error

If a type conversion error occurs after you try to execute a query, then the result set maycontain a column that is longer than 8000 bytes. This issue occurs because the maximumdata length that SQL Server supports is 8000 bytes.

To resolve this issue, modify your query to exclude the column from your result set.

Decreased Performance during Filtered Queries

When using a linked server, filtered queries may take longer than expected to execute.This issue occurs because the filters are being processed by the linked server; by default,the linked server does not pass filters to the Simba Apache Cassandra ODBC Driver withSQL Connector.

To resolve this issue, modify your query to enclose the filters in the OPENQUERYfunction. When you execute a query with the filters contained in the OPENQUERYfunction, the linked server passes the filters to the driver for processing, improvingperformance.

For example, if you execute the following query, the linked server will process the filters:SELECT TOP 100 * from [LINKEDCASSANDRA].[default].[FoodMart].[Sales]

To retrieve the same data but ensure that filtering is processed by the Simba ApacheCassandra ODBC Driver with SQL Connector instead, execute the following query:SELECT * from OPENQUERY(LINKEDCASSANDRA, 'SELECT TOP 100 *from Sales')

For more information about the OPENQUERY function, see the OPENQUERY (Transact-SQL) article in the Transact-SQL Reference available at https://msdn.microsoft.com/en-CA/library/ms188427.aspx.

www.simba.com 24




Appendix B Third Party Trademarks and Licenses

Third Party Trademarks

Apache Cassandra, Apache, and Cassandra are trademarks of The Apache SoftwareFoundation or its subsidiaries in Canada, United States and/or other countries.

Microsoft SQL Server, SQL Server, Microsoft, Access, Excel, Power BI, MSDN, Windows,Windows Server, Windows Vista, and the Windows start button are trademarks orregistered trademarks of Microsoft Corporation or its subsidiaries in Canada, UnitedStates and/or other countries.

Tableau and the Tableau logo are trademarks or registered trademarks of TableauSoftware, Inc. or its subsidiaries in Canada, United States and/or other countries.

MicroStrategy, MicroStrategy 10, and MicroStrategy Developer are trademarks orregistered trademarks of MicroStrategy, Inc. or its subsidiaries in Canada, United Statesand/or other countries.

SPSS and SPSS Statistics are trademarks or registered trademarks of IBM Corporationor its subsidiaries in Canada, United States, and/or other countries.

All other trademarks are trademarks of their respective owners.

Third Party Licenses

Boost Software License - Version 1.0 - August 17th, 2003

Permission is hereby granted, free of charge, to any person or organization obtaining acopy of the software and accompanying documentation covered by this license (the"Software") to use, reproduce, display, distribute, execute, and transmit the Software, andto prepare derivative works of the Software, and to permit third-parties to whom theSoftware is furnished to do so, all subject to the following:

The copyright notices in the Software and this entire statement, including the abovelicense grant, this restriction and the following disclaimer, must be included in all copies ofthe Software, in whole or in part, and all derivative works of the Software, unless suchcopies or derivative works are solely in the form of machine-executable object codegenerated by a source language processor.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONEDISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHERLIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUTOF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHERDEALINGS IN THE SOFTWARE.

www.simba.com 25


dtoa License

The author of this software is David M. Gay.

Copyright (c) 1991, 2000, 2001 by Lucent Technologies.

Permission to use, copy, modify, and distribute this software for any purpose without fee ishereby granted, provided that this entire notice is included in all copies of any softwarewhich is or includes a copy or modification of this software and in all copies of thesupporting documentation for such software.

THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS ORIMPLIED WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENTMAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THEMERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULARPURPOSE.

Expat

Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd

Permission is hereby granted, free of charge, to any person obtaining a copy of thissoftware and associated documentation files (the "Software"), to deal in the Softwarewithout restriction, including without limitation the rights to use, copy, modify, merge,publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons towhom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies orsubstantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNOINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHTHOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHERDEALINGS IN THE SOFTWARE.

ICU License - ICU 1.8.1 and later

COPYRIGHT AND PERMISSION NOTICE

Copyright (c) 1995-2014 International Business Machines Corporation and others

All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of thissoftware and associated documentation files (the "Software"), to deal in the Softwarewithout restriction, including without limitation the rights to use, copy, modify, merge,publish, distribute, and/or sell copies of the Software, and to permit persons to whom the

www.simba.com 26


Software is furnished to do so, provided that the above copyright notice(s) and thispermission notice appear in all copies of the Software and that both the above copyrightnotice(s) and this permission notice appear in supporting documentation.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THECOPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FORANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, ORANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA ORPROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHERTORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE ORPERFORMANCE OF THIS SOFTWARE.

Except as contained in this notice, the name of a copyright holder shall not be used inadvertising or otherwise to promote the sale, use or other dealings in this Software withoutprior written authorization of the copyright holder.

All trademarks and registered trademarks mentioned herein are the property of theirrespective owners.

libuv

libuv is part of the Node project: http://nodejs.org/

libuv may be distributed alone under Node's license:

Copyright Joyent, Inc. and other Node contributors. All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of thissoftware and associated documentation files (the "Software"), to deal in theSoftware without restriction, including without limitation the rights to use, copy,modify, merge, publish, distribute, sublicense, and/or sell copies of the Software,and to permit persons to whom the Software is furnished to do so, subject to thefollowing conditions:

The above copyright notice and this permission notice shall be included in all copiesor substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIESOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHTHOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISINGFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OROTHER DEALINGS IN THE SOFTWARE.

This license applies to all parts of libuv that are not externally maintained libraries.

www.simba.com 27


The externally maintained libraries used by libuv are:

- tree.h (from FreeBSD), copyright Niels Provos. Two clause BSD license.

- ngx_queue.h (from Nginx), copyright Igor Sysoev. Two clause BSD license.

- inet_pton and inet_ntop implementations, contained in src/inet.c, are copyright theInternet Systems Consortium, Inc., and licensed under the ISC license.

- stdint-msvc2008.h (from msinttypes), copyright Alexander Chemeris. Three clauseBSD license.

OpenSSL

Copyright (c) 1998-2011 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, arepermitted provided that the following conditions are met:1. Redistributions of source code must retain the above copyright notice, this list of

conditions and the following disclaimer.2. Redistributions in binary form must reproduce the above copyright notice, this list of

conditions and the following disclaimer in the documentation and/or other materialsprovided with the distribution.

3. All advertising materials mentioning features or use of this software must display thefollowing acknowledgment:

"This product includes software developed by the OpenSSL Project for use in theOpenSSL Toolkit. (http://www.openssl.org/)"

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorseor promote products derived from this software without prior written permission. Forwritten permission, please contact [email protected].

5. Products derived from this software may not be called "OpenSSL" nor may"OpenSSL" appear in their names without prior written permission of the OpenSSLProject.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in theOpenSSL Toolkit (http://www.openssl.org/)"

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS" AND ANYEXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THEIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITSCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITEDTO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ONANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR

www.simba.com 28


http://www.openssl.org/

http://www.openssl.org/

TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OFTHE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCHDAMAGE.

Original SSLeay License

Copyright (C) 1995-1998 Eric Young ([email protected])


This package is an SSL implementation written by Eric Young ([email protected]). Theimplementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the followingconditions are aheared to. The following conditions apply to all code found in thisdistribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSLdocumentation included with this distribution is covered by the same copyright termsexcept that the holder is Tim Hudson ([email protected]).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not tobe removed. If this package is used in a product, Eric Young should be given attribution asthe author of the parts of the library used. This can be in the form of a textual message atprogram startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, arepermitted provided that the following conditions are met:1. Redistributions of source code must retain the copyright notice, this list of conditions

and the following disclaimer.2. Redistributions in binary form must reproduce the above copyright notice, this list of

conditions and the following disclaimer in the documentation and/or other materialsprovided with the distribution.

3. All advertising materials mentioning features or use of this software must display thefollowing acknowledgement:

"This product includes cryptographic software written by Eric Young([email protected])"

The word 'cryptographic' can be left out if the rouines from the library being used arenot cryptographic related :-).

4. If you include any Windows specific code (or a derivative thereof) from the appsdirectory (application code) you must include an acknowledgement:

"This product includes software written by Tim Hudson ([email protected])"

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR ORCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

www.simba.com 29


EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITEDTO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ONANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, ORTORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OFTHE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCHDAMAGE.

The licence and distribution terms for any publically available version or derivative of thiscode cannot be changed. i.e. this code cannot simply be copied and put under anotherdistribution licence [including the GNU Public Licence.]

Stringencoders License

Copyright 2005, 2006, 2007

Nick Galbreath -- nickg [at] modp [dot] com


Redistribution and use in source and binary forms, with or without modification, arepermitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list ofconditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright notice, this list ofconditions and the following disclaimer in the documentation and/or other materialsprovided with the distribution.

Neither the name of the modp.com nor the names of its contributors may be used toendorse or promote products derived from this software without specific prior writtenpermission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ANDCONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORSBE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENTOF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; ORBUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OFLIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDINGNEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This is the standard "new" BSD license:

http://www.opensource.org/licenses/bsd-license.php

www.simba.com 30


http://www.opensource.org/licenses/bsd-license.php

Apache License, Verison 2.0

The following notice is included in compliance with the Apache License, Version 2.0 and isapplicable to all software licensed under the Apache License, Version 2.0.

Apache License

Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, and distributionas defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by the copyrightowner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all other entities thatcontrol, are controlled by, or are under common control with that entity. For thepurposes of this definition, "control" means (i) the power, direct or indirect, to causethe direction or management of such entity, whether by contract or otherwise, or (ii)ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficialownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity exercising permissionsgranted by this License.

"Source" form shall mean the preferred form for making modifications, including butnot limited to software source code, documentation source, and configuration files.

"Object" form shall mean any form resulting from mechanical transformation ortranslation of a Source form, including but not limited to compiled object code,generated documentation, and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or Object form, madeavailable under the License, as indicated by a copyright notice that is included in orattached to the work (an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object form, that isbased on (or derived from) the Work and for which the editorial revisions,annotations, elaborations, or other modifications represent, as a whole, an originalwork of authorship. For the purposes of this License, Derivative Works shall notinclude works that remain separable from, or merely link (or bind by name) to theinterfaces of, the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including the original version ofthe Work and any modifications or additions to that Work or Derivative Worksthereof, that is intentionally submitted to Licensor for inclusion in the Work by the

www.simba.com 31


http://www.apache.org/licenses/

copyright owner or by an individual or Legal Entity authorized to submit on behalf ofthe copyright owner. For the purposes of this definition, "submitted" means any formof electronic, verbal, or written communication sent to the Licensor or itsrepresentatives, including but not limited to communication on electronic mailinglists, source code control systems, and issue tracking systems that are managed by,or on behalf of, the Licensor for the purpose of discussing and improving the Work,but excluding communication that is conspicuously marked or otherwise designatedin writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalf ofwhom a Contribution has been received by Licensor and subsequently incorporatedwithin the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, eachContributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge,royalty-free, irrevocable copyright license to reproduce, prepare Derivative Worksof, publicly display, publicly perform, sublicense, and distribute the Work and suchDerivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, eachContributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge,royalty-free, irrevocable (except as stated in this section) patent license to make,have made, use, offer to sell, sell, import, and otherwise transfer the Work, wheresuch license applies only to those patent claims licensable by such Contributor thatare necessarily infringed by their Contribution(s) alone or by combination of theirContribution(s) with the Work to which such Contribution(s) was submitted. If Youinstitute patent litigation against any entity (including a cross-claim or counterclaim ina lawsuit) alleging that the Work or a Contribution incorporated within the Workconstitutes direct or contributory patent infringement, then any patent licensesgranted to You under this License for that Work shall terminate as of the date suchlitigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or DerivativeWorks thereof in any medium, with or without modifications, and in Source or Objectform, provided that You meet the following conditions:

(a) You must give any other recipients of the Work or Derivative Works a copy ofthis License; and

(b) You must cause any modified files to carry prominent notices stating that Youchanged the files; and

(c) You must retain, in the Source form of any Derivative Works that Youdistribute, all copyright, patent, trademark, and attribution notices from theSource form of the Work, excluding those notices that do not pertain to anypart of the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its distribution, then anyDerivative Works that You distribute must include a readable copy of theattribution notices contained within such NOTICE file, excluding those noticesthat do not pertain to any part of the Derivative Works, in at least one of thefollowing places: within a NOTICE text file distributed as part of the Derivative

www.simba.com 32


Works; within the Source form or documentation, if provided along with theDerivative Works; or, within a display generated by the Derivative Works, ifand wherever such third-party notices normally appear. The contents of theNOTICE file are for informational purposes only and do not modify theLicense. You may add Your own attribution notices within Derivative Worksthat You distribute, alongside or as an addendum to the NOTICE text from theWork, provided that such additional attribution notices cannot be construed asmodifying the License.

You may add Your own copyright statement to Your modifications and may provideadditional or different license terms and conditions for use, reproduction, ordistribution of Your modifications, or for any such Derivative Works as a whole,provided Your use, reproduction, and distribution of the Work otherwise complieswith the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contributionintentionally submitted for inclusion in the Work by You to the Licensor shall be underthe terms and conditions of this License, without any additional terms or conditions.Notwithstanding the above, nothing herein shall supersede or modify the terms ofany separate license agreement you may have executed with Licensor regardingsuch Contributions.

6. Trademarks. This License does not grant permission to use the trade names,trademarks, service marks, or product names of the Licensor, except as required forreasonable and customary use in describing the origin of the Work and reproducingthe content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing,Licensor provides the Work (and each Contributor provides its Contributions) on an"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, eitherexpress or implied, including, without limitation, any warranties or conditions ofTITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR APARTICULAR PURPOSE. You are solely responsible for determining theappropriateness of using or redistributing the Work and assume any risks associatedwith Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort(including negligence), contract, or otherwise, unless required by applicable law(such as deliberate and grossly negligent acts) or agreed to in writing, shall anyContributor be liable to You for damages, including any direct, indirect, special,incidental, or consequential damages of any character arising as a result of thisLicense or out of the use or inability to use the Work (including but not limited todamages for loss of goodwill, work stoppage, computer failure or malfunction, or anyand all other commercial damages or losses), even if such Contributor has beenadvised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work orDerivative Works thereof, You may choose to offer, and charge a fee for, acceptanceof support, warranty, indemnity, or other liability obligations and/or rights consistentwith this License. However, in accepting such obligations, You may act only on Yourown behalf and on Your sole responsibility, not on behalf of any other Contributor,and only if You agree to indemnify, defend, and hold each Contributor harmless for

www.simba.com 33


any liability incurred by, or claims asserted against, such Contributor by reason ofyour accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following boilerplate notice,with the fields enclosed by brackets "[]" replaced with your own identifyinginformation. (Don't include the brackets!) The text should be enclosed in theappropriate comment syntax for the file format. We also recommend that a file orclass name and description of purpose be included on the same "printed page" asthe copyright notice for easier identification within third-party archives.

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License"); you may notuse this file except in compliance with the License. You may obtain a copy ofthe License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributedunder the License is distributed on an "AS IS" BASIS, WITHOUTWARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.See the License for the specific language governing permissions andlimitations under the License.

This product includes software that is licensed under the Apache License, Version 2.0(listed below):DataStax C/C++ Driver for Apache CassandraCopyright © 2014-2015 DataStax

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this fileexcept in compliance with the License. You may obtain a copy of the License at


Unless required by applicable law or agreed to in writing, software distributed under theLicense is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONSOF ANY KIND, either express or implied. See the License for the specific languagegoverning permissions and limitations under the License.

www.simba.com 34



Documents

SimbaApacheCassandraODBC …cdn.simba.com/products/Cassandra/doc/Simba_Cassandra_ODBC_Qu… · PowerBI.Ifyouareusingthe32-bitversionofPowerBI,thenyouneedtousethe 32-bitversionofthedriver.Ifyouareusingthe64-bitversionofPowerBI,then