Quickstart Guide for Windows Simba Technologies Inc.

Transcription

1 Simba Apache Cassandra ODBC Driver Simba Technologies Inc. September 15, 2015

2 Copyright 2015 Simba Technologies Inc. All Rights Reserved. Information in this document is subject to change without notice. Companies, names and data used in examples herein are fictitious unless otherwise noted. No part of this publication, or the software it describes, may be reproduced, transmitted, transcribed, stored in a retrieval system, decompiled, disassembled, reverse-engineered, or translated into any language in any form by any means for any purpose without the express written permission of Simba Technologies Inc. Trademarks Simba, the Simba logo, SimbaEngine, SimbaEngine C/S, SimbaExpress and SimbaLib are registered trademarks of Simba Technologies Inc. All other trademarks and/or servicemarks are the property of their respective owners. Contact Us Simba Technologies Inc. 938 West 8th Avenue Vancouver, BC Canada V5Z 1E5 Tel: +1 (604) Fax: +1 (604)

3 About This Guide Purpose The Simba Apache Cassandra ODBC Driver Quickstart Guide for Windows is targeted towards users of the Simba Apache Cassandra ODBC Driver with SQL Connector, showing you how to set up your environment quickly so that you can evaluate and use the driver. Audience The guide is intended for end users of the Simba Apache Cassandra ODBC Driver with SQL Connector who want to evaluate the driver by using it in an application. Knowledge Prerequisites To use the Simba Apache Cassandra ODBC Driver, the following knowledge is helpful: Familiarity with the platform on which you are using the Simba Apache Cassandra ODBC Driver Ability to use the data source to which the Simba Apache Cassandra ODBC Driver is connecting An understanding of the role of ODBC technologies and driver managers in connecting to a data source Experience creating and configuring ODBC connections 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 text that 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. 3

4 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 9 Using Microsoft Excel 9 Using Microsoft Access 12 Using Tableau 13 Using a Linked Server 14 Using Power BI 17 Using Qlik Sense 18 Using Qlikview 18 Using SPSS Statistics 20 Contact Us 21 Appendix A Troubleshooting 22 Architecture Mismatch Problems 22 Known Issues when using Linked Server 23 Appendix B Third Party Trademarks and Licenses

5 Installing and Running Cassandra You can download Cassandra from Cassandra installation guides are available at draintro.html. The Simba Apache Cassandra ODBC Driver supports Cassandra 2.0 or later. Ensure that you download an appropriate version of Cassandra To start Cassandra: 1. Open a command prompt window: If you are using Windows 7 or earlier, click the Start button, then click All Programs, then click Accessories, and then click Command Prompt. Or, if you are using Windows 8 or later, click the arrow button at the bottom of the Start screen, then find the Windows System program group, and then click Command Prompt. 2. In the command prompt window, browse to the \bin subfolder of your Cassandra installation, and then run the following command: cassandra f If the command runs correctly, then many lines of diagnostic information appear in the window. The following line appears near the end, where PortNumber is the port on which Cassandra is listening on all interfaces for CQL client requests: Starting listening for CQL client on / :PortNumber... The following text appears as one of the last lines in the Command Prompt window: Listening for thrift clients To verify that connectivity to Cassandra is working correctly, open a new Command Prompt 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 Cassandra instance is established and the cqlsh> prompt appears as the last line in the Command Prompt window. 5

6 Importing Sample Data into Cassandra The following procedure describes how to import some sample data if you do not already have data to use. To import sample data into Cassandra: 1. Download the sample data set available at The sample data set is a modified version of the FAA data set. The original FAA data set is available for download at 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 set into the folder. 3. If you have not already done so, start Cassandra and connect to your local Cassandra instance by following the procedure in Installing and Running Cassandra on page 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 the directory where you extracted the sample data set in step 2, and then start the Cassandra shell again by running the cqlsh command. 8. To import data from the Airline.csv file into the column family that you created in step 6, run the following command: COPY faa.airline (key, "UNIQUE_CARRIER", "AIRLINE_ID", "CARRIER", "TAIL_NUM", "FL_NUM") FROM 'Airline.csv' WITH HEADER=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. 6

7 Installing the Driver The Simba Apache Cassandra ODBC Driver is available for download from On 64-bit Windows operating systems, you can execute 32- and 64-bit applications transparently. You must use the version of the driver matching the bitness of the client application accessing data in Cassandra: SimbaCassandraODBC32.msi for 32-bit applications 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, see ODBC-Data-Source-Administrator.pdf. To install the Simba Apache Cassandra ODBC Driver : 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 , 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 local computer prior to copying the file into the \lib subfolder. 7

8 Configuring the Driver To use the Simba Apache Cassandra ODBC Driver, you need to configure a Data Source Name (DSN) to connect to your data source using a client application, such as Microsoft Excel or Tableau. To create a Data Source Name: 1. Open the ODBC Administrator: If you are using Windows 7 or earlier, click the Start button, then click All Programs, then click the Simba Cassandra ODBC Driver program group corresponding to the bitness of the client application accessing data in Cassandra, and then click ODBC Administrator. Or, if you are using Windows 8 or later, on the Start screen, type ODBC administrator, and then click the ODBC Administrator search result corresponding to the bitness of the client application accessing data in Cassandra. 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 in the Host field. 5. In the Port field, type the number of the port that the Cassandra server uses to listen for client requests. By default, Cassandra uses port If your Cassandra data source is configured to use authentication, then select User Name and Password in the Authentication Type list and then type your credentials in the User and Password fields. 7. To test the connection to your Cassandra data source, ensure that Cassandra is running, and then click Test in the Simba Cassandra ODBC Driver DSN Setup dialog box. If you are prompted for authentication, type your user name and password for accessing the Cassandra instance, and then click OK The Test Results dialog box appears, displaying a message informing you whether the connection succeeded or failed. 8. Click OK to close the Test Results dialog box, and then click OK to save your DSN and close the Simba Cassandra ODBC Driver DSN Setup dialog box. For more information about configuring the Simba Apache Cassandra ODBC Driver, see the Simba Apache Cassandra ODBC Driver with SQL Connector Installation and Configuration Guide. 8

9 Connecting to the Data Source After creating a Data Source Name for connecting to your Cassandra data source, you can connect to the data source using a client application. The following are a few examples of the applications that you can use to access your data: Using Microsoft Excel on page 9 Using Microsoft Access on page 12 Using Tableau on page 13 Using a Linked Server on page 14 Using Power BI on page 17 Using Qlik Sense on page 18 Using Qlikview on page 18 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: 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 cannot filter the result set. Query Wizard Use this wizard from Microsoft Query to define and run a simple query. You can query multiple tables and columns, and sort and filter the result set. Microsoft Query Work directly in the application to define and run complex queries. For example, you can define parameterized queries and different types of joins. The following procedures are written for Microsoft Excel The Simba Apache Cassandra ODBC Driver also supports Excel Using the Data Connection Wizard 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. 9

10 If the connection fails, confirm that the bitness of the driver that you are using matches the bitness of Excel. If you are using the 32-bit version of Excel, then you need to use the 32-bit version of the driver. If you are using the 64-bit version of Excel, then you need to use the 64-bit version of the driver. For more information about diagnosing the issue, see Architecture Mismatch Problems on page From the list of tables, select the name of a table that you want to retrieve, and then click Finish. 5. In the Import Data dialog box, in the Existing Worksheet field, specify the cell where you want the top left corner of the selected table to be inserted, and then click OK. 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, you can switch from using the Query Wizard to working directly in Microsoft Query at any 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 are using matches the bitness of Excel. If you are using the 32-bit version of Excel, then you need to use the 32-bit version of the driver. If you are using the 64-bit version of Excel, then you need to use the 64-bit version of the driver. For more information about diagnosing the issue, see Architecture Mismatch Problems on page In the Query Wizard, select the tables or columns that you want to include in your query by selecting each item in the left pane and then clicking the > button. When your selection is complete, click Next. If the tables or columns that you want to include are not listed in the left pane, 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 a comparison 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 the sorting 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 to proceed. 10

11 7. Optionally, to save the query so that you can run it again without going through the process of recreating it, click Save Query, type a unique name for the query, and then click Save 8. Select Return Data To Microsoft Excel and then click Finish 9. 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. Using Microsoft 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 OK 4. 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, click Close. 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, then click Options and configure the table options as needed. 5. To define joins between your tables, in the upper pane, click and drag a field from one table to a field in another table. You can then double-click the line between the fields to modify the join. For detailed information about defining joins in Microsoft Query, see the section titled Creating, Changing, and Removing Joins in the Microsoft Query Help documentation that is provided in the application. 6. Select the columns that you want to include in your query by double-clicking the column names from the tables. You can double-click the asterisk (*) to select all the columns from a table. If Auto Query is enabled, then the results of your query automatically appear in the lower pane. Otherwise, you must click Query Now the query and see the results. 7. To filter the data in your query, click Show/Hide Criteria and then use the options in the criteria pane to define your filters. to run 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 see the results. 11

12 10. When you are finished defining your query, click Return Data to retrieve the result set in Excel. 11. 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 appears in the current Excel spreadsheet. For more information about defining complex queries using Microsoft Query, see the 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 by creating a table that links to the Cassandra data. The following procedures are written for Microsoft Access The Simba Apache Cassandra ODBC Driver also supports Access Importing Data 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 are using matches the bitness of Access. If you are using the 32-bit version of Access, then you need to use the 32-bit version of the driver. If you are using the 64-bit version of Access, then you need to use the 64-bit version of the driver. For more information about diagnosing the issue, see Architecture Mismatch Problems on page In the Import Objects dialog box, select the tables that you want to import, and then click OK. 5. In the Get External Data dialog box, select the Save import steps check box if you want to save the import process so that you can run it again at a later time, and then click 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. 12

13 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 are using matches the bitness of Access. If you are using the 32-bit version of Access, then you need to use the 32-bit version of the driver. If you are using the 64-bit version of Access, then you need to use the 64-bit version of the driver. For more information about diagnosing the issue, see Architecture Mismatch Problems on page In the Link Tables dialog box, select the tables that you want to link to, and then click OK. 5. If the Select Unique Record Identifier dialog box opens, select the column that contains the unique identifiers for the rows in the table (for example, the primary key column) 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 you selected. Using Tableau The following procedure is written for Tableau 8. The Simba Apache Cassandra ODBC Driver 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 select Other 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 are using matches the bitness of Tableau. If you are using the 32-bit version of Tableau, then you need to use the 32-bit version of the driver. If you are using the 64-bit version of Tableau, then you need to use the 64-bit version of the driver. For more information about diagnosing the issue, see Architecture Mismatch Problems on page Select the Single Table option and then click the magnifying glass to open the Select 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 click Load to see the list of tables. 5. To load the selected table, click OK. 13

14 If the following warning is displayed, click OK: This warning is displayed because Tableau sees only a generic driver and attempts to determine the capabilities of the driver. The warning does not affect how the driver will operate in Tableau. 6. In the Data Connection dialog box, click Connect live so that Tableau does not import 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 as dimensions or measures depending on the data type. You can now create reports on the table. Using a Linked Server A linked server enables you to execute distributed queries against tables stored in a Microsoft SQL Server instance and another data source. Use the Microsoft SQL Server Management Studio to link your Cassandra data source to a SQL Server instance and then execute distributed queries against both data sources. You can use either of the following methods to create the linked server: To create the linked server by using the options in the Object Explorer, see Creating a Linked Server using the Object Explorer on page 14. To create the linked server by executing stored procedures, see Creating a Linked Server 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 create your 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: 14

15 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, select Microsoft 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 for authentication, 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 the With 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 are using matches the bitness of the SQL Server instance that you are using to create the server link. For example, if you are creating the server link from a 32-bit SQL Server instance, then you need to use the 32-bit version of the driver. Contact your SQL Server administrator as needed to confirm the bitness of the server. The linked server is displayed as a node under the Linked Servers branch in the Object Explorer, and you can expand the node to browse the contents of the server down to the table level. You can now start executing distributed queries to work with data from the Cassandra data source and the SQL Server instance. For information about executing queries 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 stored procedures 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: Simba Cassandra DSN' 4. If your Cassandra data source requires a user name and password for authentication, then type the following statement, where LinkedServerName is the name of the linked server and UserName and Password are your credentials: EXEC master.dbo.sp_addlinkedsrvlogin 15

16 @rmtpassword=n'password' 5. In the toolbar at the top, click Execute. The Messages pane appears and displays a message indicating whether the statements were executed successfully. If the connection fails, confirm that the bitness of the driver that you are using matches the bitness of the SQL Server instance that you are using to create the server link. For example, if you are creating the server link from a 32-bit SQL Server instance, then you need to use the 32-bit version of the driver. Contact your SQL Server administrator as needed to confirm the bitness 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 Object Explorer, and you can expand the node to browse the contents of the server down to the table level. You can now start executing distributed queries to work with the data from the Cassandra data source and the SQL Server instance. For information about executing queries 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 available at For information about the sp_addlinkedsrvlogin stored procedure, see the sp_ addlinkedsrvlogin (Transact-SQL) article in the Transact-SQL Reference available at Querying a Linked Server Normally, you can query data by using scripts in Management Studio; however, scripts are not supported for linked servers. To execute queries against a linked server, use the editor. 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 a linked server, see Known Issues when using Linked Server on page

17 Using Power BI You can import Cassandra data into Power BI Desktop through the Power BI ODBC connector. You use a DSN connection string to connect Power BI to the database. For more information about creating connection strings for the Simba Apache Cassandra ODBC Driver, see the Simba Apache Cassandra ODBC Driver Installation and Configuration Guide. Make sure that the bitness of the driver that you are using matches the bitness of Power BI. If you are using the 32-bit version of Power BI, then you need to use the 32-bit version of the driver. If you are using the 64-bit version of Power BI, then you need to use the 64-bit version of the driver. For more information about diagnosing 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 SQL Statement (optional) and, in the field that is displayed, type or paste a SQL statement to specify the data. 5. Click OK. In the ODBC Driver dialog box, choose one: If your data store requires credentials for access, then in the Username and Password fields, type your credentials for accessing your data store, and then click Connect. Otherwise, from the column on the left, select Default or Custom and click Connect. 6. The Navigator opens, with a list of the schemas and tables that are contained in the data store. If you used a SQL statement to specify what data is returned, then only the tables 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 task pane. 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, see the Power BI Help documentation that is linked from the application. For more Power BI tutorials and how-to information, see

18 Using Qlik Sense You can import Cassandra data into a Qlik Sense app through an ODBC connection. You specify which tables and columns in your data store to load into Qlik Sense, and then construct charts and stories to analyze and present that data. Make sure that the bitness of the driver that you are using matches the bitness of Qlik 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-bit version of Qlik Sense Desktop, then you need to use the 64-bit version of the driver. For more information about diagnosing the issue, see Architecture Mismatch 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 Qlik Sense documentation that is available at Using Qlikview You can import Cassandra data into Qlikview through an ODBC connection. Qlikview's Script Editor generates a SQL script that connects to your data source and imports your data, so that you can analyze the data in Qlikview. 18

19 Make sure that the bitness of the driver that you are using matches the bitness of Qlikview. If you are using the 32-bit version of Qlikview, then you need to use the 32-bit version of the driver. If you are using the 64-bit version of Qlikview, then you need 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 the issue, 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 sure ODBC 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 Script dialog 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 use Qlikview to analyze the data in those tables. For more information about connecting to a database in Qlikview, see the Qlikview Help documentation that is linked from the application. 19

20 Using SPSS Statistics You can import Cassandra data into SPSS Statistics with a standard SQL query. The SPSS Database Wizard can automatically generate and execute an appropriate query based on parameters you specify. The following procedure is written for SPSS Statistics 23. The Simba Apache Cassandra ODBC Driver also supports earlier versions of SPSS. Make sure that the bitness of the driver that you are using matches the bitness of SPSS. If you are using the 32-bit version of SPSS, then you need to use the 32-bit version of the driver. If you are using the 64-bit version of SPSS, then you need to use the 64-bit version of the driver. For more information about diagnosing the issue, 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 the Welcome 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 Dataset window. You can now use SPSS Statistics to analyze the data. For more information about connecting to a database in SPSS Statistics, see the SPSS Statistics Help documentation that is provided in the application. 20

21 Contact Us If you have difficulty using the driver, please contact our Technical Support staff. We welcome 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 a detailed summary of the client and server environment including operating system version, patch level, and configuration. You can contact Technical Support via: support@simba.com Web site Telephone (604) Extension 3 Fax (604) You can also follow us on 21

22 Appendix A Troubleshooting Architecture Mismatch Problems If you encounter an error message similar to "The specified DSN contains an architecture mismatch between the Driver and Application", then the bitness of the application you are using to attempt to connect to the Cassandra data source does not match the bitness of the driver that you are using. You may be attempting to connect a 32-bit application to a 64-bit driver, or vice versa. Ensure that the bitness of your application matches the bitness of 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 click Account in the left pane, and then click the About Application button (where Application is the application name). 2. In the About dialog box, look for the words 32-bit or 64-bit: If the About dialog box contains 32-bit then you must use a 32-bit driver to connect to that application. If the About dialog box contains 64-bit then you must use a 64-bit driver to connect to that application. For example, the following image shows the About dialog box for a 32-bit version of Microsoft Excel

23 Known Issues when using Linked Server The following are known issues that you may encounter when using a linked server to work with your data. Scripting Options Return Errors When using a linked server, the scripting options that are accessible from the Object Explorer are not supported. For example, if you try to execute a query using one of the Script Table as options, the Management Studio will return an error message stating that the specified table "contains no columns that can be selected or the current user does not have permissions on that object". As a workaround for this issue, define your queries using the editor that opens when you click the New Query button in the toolbar instead of using the scripting options. 23

24 Type Conversion Error If a type conversion error occurs after you try to execute a query, then the result set may contain a column that is longer than 8000 bytes. This issue occurs because the maximum data 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 with SQL Connector. To resolve this issue, modify your query to enclose the filters in the OPENQUERY function. When you execute a query with the filters contained in the OPENQUERY function, the linked server passes the filters to the driver for processing, improving performance. 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 Apache Cassandra ODBC Driver 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 CA/library/ms aspx. 24

25 Appendix B Third Party Trademarks and Licenses Third Party Trademarks Apache Cassandra, Apache, and Cassandra are trademarks of The Apache Software Foundation 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 or registered trademarks of Microsoft Corporation or its subsidiaries in Canada, United States and/or other countries. Tableau and the Tableau logo are trademarks or registered trademarks of Tableau Software, Inc. or its subsidiaries in Canada, United States and/or other countries. MicroStrategy, MicroStrategy 10, and MicroStrategy Developer are trademarks or registered trademarks of MicroStrategy, Inc. or its subsidiaries in Canada, United States and/or other countries. SPSS and SPSS Statistics are trademarks or registered trademarks of IBM Corporation or 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 August 17th, 2003 Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the "Software") to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following: The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated 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 OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON- INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 25

26 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 is hereby granted, provided that this entire notice is included in all copies of any software which is or includes a copy or modification of this software and in all copies of the supporting documentation for such software. THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. 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 this software and associated documentation files (the "Software"), to deal in the Software 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 the following conditions: The above copyright notice and this permission notice shall be included in all copies or 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 WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NOINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS 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 OTHER DEALINGS IN THE SOFTWARE. ICU License - ICU and later COPYRIGHT AND PERMISSION NOTICE Copyright (c) International Business Machines Corporation and others All rights reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without 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 26

27 Software is furnished to do so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both the above copyright notice(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 OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder. All trademarks and registered trademarks mentioned herein are the property of their respective owners. libuv libuv is part of the Node project: 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 this software and associated documentation files (the "Software"), to deal in the Software 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 the following conditions: The above copyright notice and this permission notice shall be included in all copies or 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 WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS 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 OTHER DEALINGS IN THE SOFTWARE. This license applies to all parts of libuv that are not externally maintained libraries. 27

28 The externally maintained libraries used by libuv are: OpenSSL - 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 the Internet Systems Consortium, Inc., and licensed under the ISC license. - stdint-msvc2008.h (from msinttypes), copyright Alexander Chemeris. Three clause BSD license. Copyright (c) The OpenSSL Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted 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 materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. ( 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org. 5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project. 6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit ( THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR 28