simbamongodbodbcdriverwith sqlconnector ...cdn.simba.com/products/mongodb/doc/simba_mongodb... ·...

Simba MongoDB ODBC Driver withSQL Connector

Quickstart Guide for Windows

Simba Technologies Inc.

February 25, 2016

Copyright © 2016 Simba Technologies Inc. All Rights Reserved.

Information in this document is subject to change without notice. Companies, namesand data 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, ortranslated into any language in any form by any means for any purpose without theexpress written permission of Simba Technologies Inc.

Trademarks

Simba, the Simba logo, SimbaEngine, and Simba Technologies are registeredtrademarks of Simba Technologies Inc. in Canada, United States and/or othercountries. All other trademarks and/or servicemarks are the property of their respectiveowners.

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 MongoDB ODBC Driver with SQLConnector Quickstart Guide for Windows

http://www.simba.com/

About This Guide

PurposeThe Simba MongoDB ODBC Driver with SQL Connector Quickstart Guide forWindows provides basic configuration instructions for the Simba MongoDB ODBCDriver with SQL Connector, and explains how to use the driver in various applicationsso that you can evaluate and use the driver on a Windows machine.

AudienceThe guide is intended for end users of the Simba MongoDB ODBC Driver with SQLConnector who want to quickly set up a basic connection in order to evaluate and usethe Windows driver. For more comprehensive information about configuring and usingthe driver, see the Simba MongoDB ODBC Driver with SQL Connector Installation andConfiguration Guide.

Knowledge PrerequisitesTo use the Simba MongoDB ODBC Driver with SQL Connector, the followingknowledge is helpful:

l Familiarity with the platform on which you are using the Simba MongoDB ODBCDriver with SQL Connector

l Ability to use the data store to which the Simba MongoDB ODBC Driver withSQL Connector is connecting

l An understanding of the role of ODBC technologies and driver managers inconnecting to a data store

l Experience creating and configuring ODBC connectionsl Exposure to SQL

Document ConventionsItalics are used when referring to book and document titles.

Bold is used in procedures for graphical user interface elements that a user clicks andtext 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.

www.simba.com 3


Table of Contents

About the SimbaMongoDB ODBC Driver with SQLConnector 5

AccessingMongoDB 6

Installing and Configuring the Driver 7Installing the Driver 7Configuring the Driver 8

Connecting to the Data Store 10UsingMicrosoft Access 10UsingMicrosoft Excel 11UsingMicrosoft Power BI 14UsingMicroStrategy 15Using Qlik Sense 17Using QlikView 18Using SPSS Statistics 19Using a SQL Server Linked Server 20Using Tableau 22Using TIBCOSpotfire 23

Contact Us 25

Appendix A Troubleshooting 26ArchitectureMismatch Problems 26Known Issues WhenUsingMicrosoft Office 27Known Issues WhenUsing Linked Server 29

Third-Party Trademarks 30

Third-Party Licenses 31

www.simba.com 4


About the Simba MongoDBODBC Driver with SQLConnector

The Simba MongoDB ODBC Driver with SQL Connector enables BusinessIntelligence (BI), analytics, and reporting on data that is stored in MongoDB databases.The driver complies with the ODBC 3.80 data standard and adds importantfunctionality such as Unicode, as well as 32- and 64-bit support for high-performancecomputing environments on all platforms.

ODBC is one of the most established and widely supported APIs for connecting to andworking with databases. At the heart of the technology is the ODBC driver, whichconnects an application to the database. For more information about ODBC, seehttp://www.simba.com/resources/data-access-standards-library. For completeinformation about the ODBC specification, see the ODBC API Reference athttp://msdn.microsoft.com/en-us/library/windows/desktop/ms714562(v=vs.85).aspx.

The Simba MongoDB ODBC Driver with SQL Connector is available for Microsoft®Windows®, Linux, and Mac OS X platforms.

www.simba.com 5


http://www.simba.com/resources/data-access-standards-library

http://msdn.microsoft.com/en-us/library/windows/desktop/ms714562(v=vs.85).aspx

AccessingMongoDB

For the purposes of this Quickstart Guide for Windows, it is assumed that you alreadyhave a MongoDB database that you can query.

For information about installing, configuring, and running MongoDB, see theappropriate Getting Started Guide from MongoDB:https://docs.mongodb.org/manual/#getting-started.

www.simba.com 6


https://docs.mongodb.org/manual#getting-started

Installing and Configuring the Driver

To set up the Simba MongoDB ODBC Driver with SQL Connector to connect to yourdata store, do the following:

l Install the driver on the machine that you use to access the data. For moreinformation, see Installing the Driver on page 7.

l Configure the driver by creating a Data Source Name (DSN) that specifies thenecessary connection properties. For more information, see Configuring theDriver on page 8.

Installing the DriverThe Simba MongoDB ODBC Driver with SQL Connector is available for download athttp://www.simba.com/drivers/mongodb-odbc-jdbc.

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 MongoDB:

l SimbaMongoDBODBC32.msi for 32-bit applicationsl SimbaMongoDBODBC64.msi for 64-bit applications

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

You install the Simba MongoDB ODBC Driver with SQL Connector on client machinesthat access data stored in MongoDB databases. Each machine that you install thedriver on must meet the following minimum system requirements:

l One of the following operating systems:o Windows 7 SP1, 8, or 8.1o Windows Server 2008 R2 SP1, 2012, or 2012 R2

l 600 MB of available disk space

To install the driver, you must have Administrator privileges on the machine.

The driver supports MongoDB versions 2.4, 2.6, and 3.0.

To install the Simba MongoDB ODBC Driver with SQL Connector:

1. Depending on the bitness of your client application, double-click to runSimbaMongoDBODBC32.msi or SimbaMongoDBODBC64.msi.

2. Click Next.3. Select the check box to accept the terms of the License Agreement if you agree,

and then click Next.

www.simba.com 7


http://www.simba.com/drivers/mongodb-odbc-jdbc

4. To change the installation location, click Change, then browse to the desiredfolder, 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 above.To avoid security issues, you might need to save the license file on your localmachine prior to copying the file into the \lib subfolder.

Configuring the DriverTo use the Simba MongoDB ODBC Driver with SQL Connector in a client application,you need to configure a Data Source Name (DSN) to connect to your data store.

To create a Data Source Name:

1. Open the ODBC Administrator:l If you are using Windows 7 or earlier, click Start , then click AllPrograms, then click the Simba MongoDB ODBC Driver program groupcorresponding to the bitness of the client application accessing data inMongoDB, and then click ODBC Administrator.

l Or, if you are using Windows 8 or later, on the Start screen, type ODBCadministrator, and then click the ODBC Administrator search resultcorresponding to the bitness of the client application accessing data inMongoDB.

2. Click the System DSN tab.3. In the list of DSNs, select Simba MongoDB DSN, and then click Configure.4. In the Server field, type the IP address or host name of the MongoDB instance.

If you are running MongoDB on your local machine, then type localhost inthe Server field.

5. In the Port field, type the number of the TCP port that the MongoDB server usesto listen for client requests.

By default, MongoDB uses port 27017.6. In the Database field, type the name of the database that you want to access.7. If your MongoDB server is configured to use authentication, then select the

appropriate authentication mechanism from the Mechanism drop-down list andprovide the necessary credentials and authentication settings in the fields belowthe list.

For detailed information about configuring authentication, see the SimbaMongoDB ODBC Driver with SQL Connector Installation and ConfigurationGuide.

www.simba.com 8


8. To test the connection to your MongoDB data store, click Test in the SimbaMongoDB ODBC Driver DSN Setup dialog box.

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

9. Click OK to close the Test Results dialog box, and then click OK to save yourDSN and close the Simba MongoDB ODBC Driver DSN Setup dialog box.

For more information about configuring the Simba MongoDB ODBC Driver withSQL Connector, including how to modify or update the schema definition used forthe MongoDB data store, see the Simba MongoDB ODBC Driver with SQLConnector Installation and Configuration Guide.

www.simba.com 9


Connecting to the Data Store

After creating a Data Source Name for connecting to your MongoDB data store, youcan connect to the data store using a client application. The following are a fewexamples of the applications that you can use to access your data:

l Using Microsoft Access on page 10l Using Microsoft Excel on page 11l Using Microsoft Power BI on page 14l Using MicroStrategy on page 15l Using Qlik Sense on page 17l Using QlikView on page 18l Using SPSS Statistics on page 19l Using a SQL Server Linked Server on page 20l Using Tableau on page 22l Using TIBCO Spotfire on page 23

Using Microsoft AccessIn Microsoft Access, you can connect to MongoDB data by using either of the followingmethods:

l To import the data, see Importing Data on page 10.l To create a table that links to the data, see Linking to Data on page 11.

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

Make sure that the bitness of the driver that you are using matches the bitness ofAccess. 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 needto use the 64-bit version of the driver. For more information about diagnosing theissue, see "Architecture Mismatch Problems" in Troubleshooting on page 26.

ImportingData

To import MongoDB data:

1. In Access, select the External Data tab in the ribbon and then click ODBCDatabase.

2. Select Import the Source Data into a New Table in the Current Database andthen click OK.

3. In the Select Data Source dialog box, select the Machine Data Source tab, thenselect your DSN from the list, and then click OK.

www.simba.com 10


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

5. In the Get External Data dialog box, select the Save Import Steps check box ifyou 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.For information about known issues that you might encounter while using theSimba MongoDB ODBC Driver with SQL Connector in Microsoft Access, see"Known Issues when Using Microsoft Office" in Troubleshooting on page 26.

Linking to Data

To link to MongoDB data:

1. In Access, select the External Data tab in the ribbon and then click ODBCDatabase.

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 your DSN from the list, and then click OK.4. 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 primarykey column) and then click OK. You might be prompted to do this for multipletables.

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

For information about known issues that you might encounter while using theSimba MongoDB ODBC Driver with SQL Connector in Microsoft Access, see"Known Issues when Using Microsoft Office" in Troubleshooting on page 26.

Using Microsoft ExcelIn Microsoft Excel, you can connect to MongoDB data by using one of the followingtools:

l Data Connection Wizard: Use this wizard to retrieve a table from MongoDB.When using this wizard, you can only retrieve a single table at a time, and youcannot filter the result set. For more information, see Using the Data ConnectionWizard on page 12.

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 resultset. For more information, see Using the Query Wizard on page 12.

www.simba.com 11


l Microsoft Query: Work directly in the application to define and run complexqueries. For example, you can define parameterized queries and different typesof joins. For more information, see Using Microsoft Query on page 13.

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

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

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 theGet External Data group, and then click From Data Connection Wizard.

2. In the Data Connection Wizard, selectODBC DSN in the list of data sourcetypes, and then click Next.

3. In the list of ODBC data sources, select your DSN, and then click Next.4. 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 thenclick 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, 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 theGet External Data group, and then click From Microsoft Query.

2. In the Choose Data Source dialog box, on the Databases tab, select your DSN.3. Make sure that the Use the Query Wizard to Create/Edit Queries check box is

selected, and then click OK.4. 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. Whenyour 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.

www.simba.com 12


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 descendingorder. Repeat as needed to define additional levels of sorting, and then clickNext to proceed.

7. Optionally, to save the query so that you can run it again without going throughthe 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.If the query fails and you encounter an error message stating "Qualifiedcolumn could not be bound", then the result set might contain column namesthat are not valid in Microsoft Query. For more information, see "KnownIssues when Using Microsoft Office" in Troubleshooting on page 26.

9. In the Import Data dialog box, in the Existing Worksheet field, specify the cellwhere you want the first column header of the result set to appear, and then clickOK.

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 theGet External Data group, and then click From Microsoft Query.

2. In the Choose Data Source dialog box, on the Databases tab, select your 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 iscomplete, click Close. If necessary, you can reopen the dialog box to add moretables by clicking Add Table(s) .

If the tables that you want to include are not listed in the dialog box, then clickOptions and configure the table options as needed.

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

For detailed information about defining joins in Microsoft Query, see the"Creating, Changing, and Removing Joins" section in the Microsoft QueryHelp documentation that is provided in the application.

www.simba.com 13


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 allthe columns 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 andsee the results.

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 cellwhere you want the first column header of the result set to appear, and then clickOK.

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 Power BIYou can import MongoDB data into Microsoft Power BI through an ODBC connection.

The following procedure is written for Power BI Desktop 2.30.4246.181. The SimbaMongoDB ODBC Driver with SQL Connector also supports earlier versions of PowerBI Desktop.

Make sure that the bitness of the driver that you are using matches the bitness ofPower BI Desktop. If you are using the 32-bit version of Power BI Desktop, thenyou need to use the 32-bit version of the driver. If you are using the 64-bit versionof Power BI Desktop, then you need to use the 64-bit version of the driver. Formore information about diagnosing the issue, see "Architecture MismatchProblems" in Troubleshooting on page 26.

To retrieve data from your MongoDB data store using Power BI:

1. In Power BI Desktop, click Get Data.2. In the Get Data dialog box, click Other, then selectODBC from the list of data

source types, and then click Connect.

www.simba.com 14


3. In the From ODBC dialog box, in the Data Source Name (DSN) drop-down list,select your DSN.

4. Optionally, to specify what data is returned with a SQL statement, expand theAdvanced Options area and then, in the SQL Statement (Optional) field, typeor paste a SQL statement to specify the data.

5. Click OK. If you are prompted to provide your credentials, then do one of thefollowing:

l If your data store requires credentials for access, then in the Username andPassword 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 thenclick Connect.

A dialog box opens and displays the data that is returned from the data store. Ifyou used a SQL statement to specify what data is returned, then the dialog boxonly displays the rows returned by the SQL statement.

6. Choose one:l If you did not use a SQL statement to select your data, then select the checkboxes next to the tables that you want to import and click Load.

l Or, if you used a SQL statement to select your data, click Load.

The selected data is loaded into Power BI Desktop and listed in the Fields task pane.You can now use Power BI to analyze the data.

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

For more Power BI tutorials and how-to information, seehttps://powerbi.microsoft.com/en-us/documentation/powerbi-service-get-started.

Using MicroStrategyYou can analyze your MongoDB data in MicroStrategy by accessing it through aMicroStrategy database instance. You can then import that data into a MicroStrategyproject, and create facts, attributes, and metrics to analyze it.

The following steps are written for MicroStrategy 10. The Simba MongoDB ODBCDriver with SQL Connector also supports earlier versions of MicroStrategy. Consult theMicroStrategy Readme for your version of MicroStrategy to determine whether yourdatabase is supported as a MicroStrategy data warehouse.

Make sure that you are using the 64-bit version of your driver. MicroStrategy 10 is a64-bit application.

www.simba.com 15


https://powerbi.microsoft.com/en-us/documentation/powerbi-service-get-started

To add your MongoDB data to a MicroStrategy project:

1. In MicroStrategy Developer, connect to the project source containing the projectthat you want to add your data to. For instructions on connecting to a projectsource, see the MicroStrategy Developer Help documentation that is provided inthe application.

Make sure that you have administrative privileges for the project source.2. In the tree view, expand your project source, and then select Administration >

Configuration Managers > Database Instances.3. Select File > New > Database Instance.4. In the Database Instances dialog box, in the Database Instance Name field,

type a name for your new database instance.5. From the Database Connection Type drop-down list, select your database type.6. Click New.7. In the Database Connections dialog box, from the list of available database

connectors, select your DSN.8. Click New.9. In the Database Logins dialog box, in the Database Login field, type a name for

your new database login.10. Click OK to save the database login and close the Database Logins dialog box.11. In the list of database logins, make sure that the new database login is selected,

and then click OK to save the database connection and close the DatabaseConnections dialog box.

12. In the list of database connections, make sure that the new database connectionis selected, and then click OK to save the database instance and close theDatabase Instances dialog box.

13. Restart Intelligence Server.14. In MicroStrategy Developer, open the project that you want to add your data to.

Make sure the project is selected in the tree view.15. Select Schema >Warehouse Catalog.16. In the Warehouse Catalog, do one of the following:

l If you are connecting to a new project, then from the Select DefaultDatabase Instance drop-down list, select the new database instance andclick OK.

l Or, if you are adding your data to an existing project, then from the SelectDatabase Instance drop-down list, select the new database instance.

All of the tables that are available in the project are displayed in the TablesAvailable area.

17. From the Tables Available area, select the tables that you want to add to theproject. Click > to add those tables to the list of tables being used by the project.

www.simba.com 16


18. When you are done adding tables to the project, click Save and Close. TheWarehouse Catalog closes.

Data from the specified tables in your database can now be used to create facts andattributes in the MicroStrategy project.

For more information about connecting to a database in MicroStrategy, see theMicroStrategy Help documentation that is provided in the application.

Using Qlik SenseYou can import MongoDB 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, andthen construct charts and stories to analyze and present that data.

The following procedure is written for Qlik Sense Desktop 2.1. The Simba MongoDBODBC Driver with SQL Connector also supports earlier versions of Qlik SenseDesktop.

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, thenyou need to use the 32-bit version of the driver. If you are using the 64-bit versionof Qlik Sense Desktop, then you need to use the 64-bit version of the driver. Formore information about diagnosing the issue, see "Architecture MismatchProblems" in Troubleshooting on page 26.

To retrieve data from your MongoDB data store using Qlik Sense:

1. In Qlik Sense Desktop, from the Qlik Sense Desktop Hub, click Create NewApp.

2. In the Create New App dialog box, type the name of your new app and clickCreate, and then click Open App.

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

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

DSN and the correct bitness for your version of Qlik Sense Desktop are selected.6. From the list of data sources, select your 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 Next .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.

www.simba.com 17


11. When you are done selecting the tables and columns that you need, click Loadand Finish. The Select Data dialog box closes and the Data Loading dialog boxopens.

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 help site: https://help.qlik.com.

Using QlikViewYou can import MongoDB data into QlikView through an ODBC connection. QlikView'sScript Editor generates a SQL script that connects to your data store and imports yourdata, so that you can analyze the data in QlikView.

The following procedure is written for QlikView 12. The Simba MongoDB ODBC Driverwith SQL Connector also supports earlier versions of QlikView.

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" in Troubleshooting on page 26.

To retrieve data from your MongoDB data store using QlikView:

1. In QlikView, select 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 list, make sure thatODBC is

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

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. Note the

results in the Connection to Data Source Test dialog box and then click OK toclose it.

7. Click OK. The Connect to Data Source dialog box closes and an ODBCCONNECT statement is displayed in the main script area of the Edit Script dialogbox.

8. Click Select.9. In the Create Select Statement dialog box, select the data that you want to

analyze in QlikView by doing the following:

www.simba.com 18


https://help.qlik.com/

a. From the Database Tables list, select a table that contains data that youwant to analyze.

b. From the Fields list, select the fields that contain data that you want toanalyze in QlikView.

c. Click Add.

To select data from other tables, repeat these steps as needed.10. When you are done selecting the data to include in your app, click OK to close

the Create Select Statement dialog box.11. 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.12. Click OK to close the Edit Script dialog box.13. Select File > Reload.

The script is executed and the specified tables are loaded into QlikView. You can nowuse QlikView to analyze the data in those tables.

For more information about connecting to a database in QlikView, see the QlikViewhelp site: https://help.qlik.com.

Using SPSS StatisticsYou can import MongoDB 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 MongoDB ODBCDriver 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" in Troubleshooting on page 26.

To retrieve data from your MongoDB data store using SPSS:

1. In SPSS Statistics, select File > Open Database > New Query. The DatabaseWizard opens at the Welcome page.

2. From the ODBC Data Source list, select your 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.

www.simba.com 19


https://help.qlik.com/

6. On the Limit Retrieved Cases page, specify how to limit the data you retrieve andthen click Next.

7. On the Define Variables page, specify how SPSS should define those variablesand 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 newDataset window. 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.

Using a SQL Server Linked ServerA linked server enables you to execute distributed queries against tables stored in aMicrosoft SQL Server instance and another data store. Use the Microsoft SQL ServerManagement Studio to link your MongoDB data store to a SQL Server instance andthen execute distributed queries against both data stores.

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, seeCreating a Linked Server using the Object Explorer on page 20.

l To create the linked server by executing stored procedures, see Creating aLinked Server using Stored Procedures on page 21.

Make sure that the bitness of the driver that you are using matches the bitness ofthe SQL Server instance that you are using to create the server link. If you arecreating the server link from a 32-bit SQL Server instance, then you need to usethe 32-bit version of the driver. If you are creating the server link from a 64-bitSQL Server instance, then you need to use the 64-bit version of the driver. Contactyour SQL Server administrator as needed to confirm the bitness of the server. Formore information about diagnosing the issue, see "Architecture MismatchProblems" in Troubleshooting on page 26.

Creating a Linked Server using the Object Explorer

You can use the options available in the user interface of the Management Studio tocreate 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.

www.simba.com 20


3. In the New Linked Server dialog box, use the options on the General page toconfigure your linked server:a. In the Linked Server field, type a name for your linked server.b. Under Server Type, selectOther Data Source.c. In the Provider drop-down list, selectMicrosoft OLE DB Provider for

ODBC Drivers.d. In the Data Source field, type the name of your DSN. For example, type

Simba MongoDB ODBC DSN.4. Click OK to save your settings and link the MongoDB data store to the SQL

Server instance.

The linked server is displayed as a node under the Linked Servers branch in theObject Explorer, and you can expand the node to browse the contents of the serverdown to the table level. You can now start executing distributed queries to work withdata from the MongoDB data store and the SQL Server instance. For information aboutexecuting queries against the linked server, see Querying a Linked Server on page 22.

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 NewQuery.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'MONGODB',@provider=N'MSDASQL', @datasrc=N'Simba MongoDB ODBCDSN'

4. In the toolbar at the top, click Execute.

The Messages pane opens and displays a message indicating whether thestatements were executed successfully.

5. 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 tothe table level. You can now start executing distributed queries to work with the datafrom the MongoDB data store and the SQL Server instance. For information aboutexecuting queries against the linked server, see Querying a Linked Server on page 22.

www.simba.com 21


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

For information about the sp_addlinkedsrvlogin stored procedure, see "sp_addlinkedsrvlogin (Transact-SQL)" in the Transact-SQL Reference: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, scriptsare not supported for linked servers. To execute queries against a linked server, usethe editor.

To query a linked server:

1. In the toolbar at the top of Management Studio, click NewQuery.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 IssuesWhen Using Linked Server" in Troubleshootingon page 26.

Using TableauYou can work with MongoDB data in Tableau through an ODBC connection. TheSimba MongoDB ODBC Driver with SQL Connector includes a Tableau Data-connection Customization (TDC) file for Windows that helps configure Tableau tooperate more efficiently using the driver.

The following procedures are written for Tableau 8. The Simba MongoDB ODBCDriver with SQL Connector also supports Tableau 7.

Make sure that the bitness of the driver that you are using matches the bitness ofTableau. If you are using the 32-bit version of Tableau, then you need to use the32-bit version of the driver. If you are using the 64-bit version of Tableau, then youneed to use the 64-bit version of the driver. For more information about diagnosingthe issue, see "Architecture Mismatch Problems" in Troubleshooting on page 26.

To install the .TDC file:

1. Copy the file named Simba MongoDB ODBC Driver.tdc from the driverinstallation directory to the Documents\My TableauRepository\DataSources directory.

2. Restart Tableau.

www.simba.com 22


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


To connect 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 Generic ODBC Connection dialog box, in the DSN drop-down list, selectyour DSN and then click Connect.

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 might need to clickLoad to see the list of tables.

5. To load the selected table, click OK.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 MongoDB.

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 onthe table.

Using TIBCO SpotfireYou can work with MongoDB data in TIBCO Spotfire through an ODBC connection.

The following procedure is written for TIBCO Spotfire Analyst 7.5. The SimbaMongoDB ODBC Driver with SQL Connector also supports other Spotfire clients,including those from Spotfire 6.5 and 7.0.

To connect to your MongoDB data store using TIBCO Spotfire Business Author,you must install the Simba MongoDB ODBC Driver with SQL Connector andconfigure a DSN on the machine where Spotfire Business Author is running.Make sure that the bitness of the driver that you are using matches the bitness ofyour operating system. If you are using a 32-bit operating system, then you need touse the 32-bit version of the driver. If you are using a 64-bit operating system, thenyou need to use the 64-bit version of the driver.

To retrieve data from your MongoDB data store using Spotfire Analyst:

1. In TIBCO Spotfire Analyst, select File > Add Data Tables, and then click Add> Database.

2. In the Open Database dialog box, selectODBC Data Provider and then clickConfigure.

3. In the Configure Data Source Connection dialog box, from the System Or UserData Source drop-down list, select your DSN.

4. If the data store that you are connecting to requires authentication, then type yourcredentials in the Username and Password fields.

www.simba.com 23


5. Click OK.6. In the Open Database dialog box, click OK.7. In the Specify Tables And Columns dialog box, in the Tables, Views, And

Columns pane, select the check boxes beside the items that you want to retrieve.

Optionally, you can edit the SQL statement manually in the SQL Statement pane,or load a statement from a SQL file.

8. In the Data Source Name field, type a name for the data source in Spotfire, andthen click OK.

9. To preview the data table that is retrieved based on your selected data, in theAdd Data Tables dialog box, click Preview. To close the preview, click Close.

10. In the Add Data Tables dialog box, click OK.

Data retrieved from your selected tables, columns, and views displays in the Datapanel.

www.simba.com 24


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 25


http://www.simba.com/

Appendix A Troubleshooting

For information about possible workarounds or solutions for known issues that youmight encounter while using the driver in various BI tools, see the following sections:

l Architecture Mismatch Problems on page 26l Known Issues When Using Microsoft Office on page 27l Known Issues When Using Linked Server on page 29

Architecture Mismatch ProblemsIf you encounter an error message similar to "The specified DSN contains anarchitecture mismatch between the Driver and Application", then the bitness of theapplication you are using to attempt to connect to the MongoDB data store does notmatch the bitness of the driver that you are using. You might be attempting to connect a32-bit application to a 64-bit driver, or vice versa. Make sure that the bitness of yourapplication 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 Aboutdialog box for Microsoft Office 2013 products, select 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:l If the About dialog box contains 32-bit then you must use a 32-bit driver toconnect to that application.

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

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

www.simba.com 26


of Microsoft Excel 2013.

Known Issues When Using Microsoft OfficeThe following are known issues that you might encounter when using Microsoft Queryor Microsoft Access to work with your data.

Invalid Primary Keys

In Microsoft Access, if a table contains cells that show #Deleted as the value instead ofthe expected data value, then the table might be using an invalid primary key. Todiagnose this issue, check the primary key values in the table and the data type of theprimary key column, and verify if either of the following situations apply.

Primary Key Value is not Unique

Access does not allow primary keys to be used by more than one row in the sametable. Each primary key in a table must be unique.

www.simba.com 27


To resolve this issue, make sure that the table does not contain any rows that share thesame primary key value.

Primary Key Column is of an Unsupported Type

Access does not support the following data types for primary key columns:

l SQL_BIGINTl SQL_WCHARl SQL_WVARCHARl SQL_WLONGVARCHAR

To resolve this issue, convert the column to another data type, such as SQL_INTEGERor SQL_CHAR.

Invalid Column Names

In Microsoft Access, if you encounter an error message stating "[ColumnName] is not avalid name" (where [ColumnName] is the name of a column in your result set), then thecolumn name contains special characters that are not supported by the application.

In Microsoft Query, this issue returns an error message stating "Qualified column couldnot be bound".

The issue might be caused by the separator characters that the driver uses whengenerating a schema definition. To resolve this issue, change the ODBC column namein the schema definition to a valid name, based on the following guidelines:

l The column name starts with a letter of the alphabet or an underscore (_).l The column name only contains characters that are a letter of the alphabet, anumber, or an underscore (_).

To rename columns in the schema definition:

1. In the Schema Editor, open the local file containing the schema definition thatyou are using for the connection.

2. In the left pane, select the table containing the column that has the invalid name.3. In the main pane, change the SQL Name value of the column to a valid column

name.

The SQL Name value is the column name that is exposed in the ODBC layer.4. Save your changes to the schema definition.

After reconnecting to the data store using the new schema definition, you should beable to retrieve the column successfully.

For more information about using the Schema Editor, see the Schema Editor UserGuide for ODBC Connections.

www.simba.com 28


Known Issues When Using Linked ServerThe following are known issues that you might encounter when using a SQL Serverlinked server to work with 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 statingthat the specified table "contains no columns that can be selected or the current userdoes not have permissions on that object".

As a workaround for this issue, define your queries using the editor that opens whenyou click the NewQuery button in the toolbar instead of using the scripting options.

Type Conversion Error

If a type conversion error occurs after you try to execute a query, then the result setmight contain a column that is longer than 8000 bytes. This issue occurs because themaximum 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 might take longer than expected toexecute. This issue occurs because the filters are being processed by the linkedserver; by default, the linked server does not pass filters to the Simba MongoDB ODBCDriver with SQL 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 thefilters:

SELECT TOP 100 * from [LINKEDMONGODB].[default].[FoodMart].[Sales]

To retrieve the same data but make sure that filtering is processed by the SimbaMongoDB ODBC Driver with SQL Connector instead, execute the following query:

SELECT * from OPENQUERY(LINKEDMONGODB, 'SELECT TOP 100 *from Sales')

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

www.simba.com 29




Third-Party Trademarks

Linux is the registered trademark of Linus Torvalds in Canada, United States and/orother countries.

Mac, Mac OS, and OS X are trademarks or registered trademarks of Apple, Inc. or itssubsidiaries in Canada, United States and/or other countries.

MongoDB and Mongo are trademarks or registered trademarks of MongoDB, Inc. or itssubsidiaries 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 aretrademarks or registered trademarks of Microsoft Corporation or its subsidiaries inCanada, United States 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, UnitedStates and/or other countries.

Qlik, QlikView, QlikSense, and Qlik Sense are trademarks or registered trademarks ofQlikTech International AB or its subsidiaries in Canada, United States and/or othercountries.

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

TIBCO, Spotfire, TIBCO Spotfire, TIBCO Spotfire Analyst, and TIBCO SpotfireBusiness Author are trademarks or registered trademarks of TIBCO Software Inc. or itssubsidiaries in Canada, United States, and/or other countries.

All other trademarks are trademarks of their respective owners.

www.simba.com 30


Third-Party Licenses

The licenses for the third-party libraries that are included in this product are listedbelow.

Cyrus SASL License

Copyright (c) 1994-2012 Carnegie Mellon University. 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 othermaterials provided with the distribution.

3. The name "Carnegie Mellon University" must not be used to endorse or promoteproducts derived from this software without prior written permission. Forpermission or any other legal details, please contactOffice of Technology TransferCarnegie Mellon University5000 Forbes AvenuePittsburgh, PA 15213-3890(412) 268-4387, fax: (412) [email protected]

4. Redistributions of any form whatsoever must retain the followingacknowledgment:"This product includes software developed by Computing Services at CarnegieMellon University (http://www.cmu.edu/computing/)."

CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITHREGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS, IN NO EVENT SHALL CARNEGIE MELLONUNIVERSITY BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIALDAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OFUSE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR INCONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

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 withoutfee is hereby granted, provided that this entire notice is included in all copies of any

www.simba.com 31


mailto:[email protected]

http://www.cmu.edu/computing/

software which is or includes a copy or modification of this software and in all copies ofthe supporting 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 CONCERNINGTHE MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANYPARTICULAR PURPOSE.

Expat License

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 permitpersons 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 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 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, ARISINGFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OROTHER DEALINGS 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 whomthe 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 abovecopyright 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 WARRANTIESOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THECOPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE

www.simba.com 32


FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES,OR ANY 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 Softwarewithout prior written authorization of the copyright holder.

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

OpenSSL License

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



3. All advertising materials mentioning features or use of this software must displaythe following 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 toendorse or promote products derived from this software without prior writtenpermission. For written 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 theOpenSSL Project.

6. Redistributions of any form whatsoever must retain the followingacknowledgment:

"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,THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSLPROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

www.simba.com 33


http://www.openssl.org/

http://www.openssl.org/

OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDINGNEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OFTHIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young([email protected]).This product includes software written by Tim Hudson ([email protected]).

Original SSLeay License

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


This package is an SSL implementation written by Eric Young ([email protected]).The implementation 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. TheSSL documentation included with this distribution is covered by the same copyrightterms except that the holder is Tim Hudson ([email protected]).

Copyright remains Eric Young's, and as such any Copyright notices in the code are notto be removed. If this package is used in a product, Eric Young should be givenattribution as the author of the parts of the library used. This can be in the form of atextual message at program startup or in documentation (online or textual) providedwith 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



3. All advertising materials mentioning features or use of this software must displaythe following 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 usedare not 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])"

www.simba.com 34


THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESSOR IMPLIED 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, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUTNOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The licence and distribution terms for any publically available version or derivative ofthis code cannot be changed. i.e. this code cannot simply be copied and put underanother distribution 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 listof conditions and the following disclaimer in the documentation and/or othermaterials provided with the distribution.

Neither the name of the modp.com nor the names of its contributors may be usedto endorse or promote products derived from this software without specific priorwritten permission.

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 ORCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUTNOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

www.simba.com 35


ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This is the standard "new" BSD license:

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

Apache License, Version 2.0

The following notice is included in compliance with the Apache License, Version 2.0and is applicable 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, anddistribution as 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)beneficial ownership 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, includingbut not limited to software source code, documentation source, and configurationfiles.

"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 inor attached 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 not

www.simba.com 36


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

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

include 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 thecopyright owner or by an individual or Legal Entity authorized to submit on behalfof the copyright owner. For the purposes of this definition, "submitted" means anyform of 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 managedby, or on behalf of, the Licensor for the purpose of discussing and improving theWork, but excluding communication that is conspicuously marked or otherwisedesignated in 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 subsequentlyincorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License,each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepareDerivative Works of, publicly display, publicly perform, sublicense, and distributethe Work and such Derivative 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 licenseto make, have made, use, offer to sell, sell, import, and otherwise transfer theWork, where such license applies only to those patent claims licensable by suchContributor that are necessarily infringed by their Contribution(s) alone or bycombination of their Contribution(s) with the Work to which such Contribution(s)was submitted. If You institute patent litigation against any entity (including across-claim or counterclaim in a lawsuit) alleging that the Work or a Contributionincorporated within the Work constitutes direct or contributory patentinfringement, then any patent licenses granted to You under this License for thatWork shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work orDerivative Works thereof in any medium, with or without modifications, and inSource or Object form, 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 any

www.simba.com 37


part 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 DerivativeWorks; 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 mayprovide additional or different license terms and conditions for use, reproduction,or distribution 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, anyContribution intentionally submitted for inclusion in the Work by You to theLicensor shall be under the terms and conditions of this License, without anyadditional terms or conditions. Notwithstanding the above, nothing herein shallsupersede or modify the terms of any separate license agreement you may haveexecuted with Licensor regarding such 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 requiredfor reasonable and customary use in describing the origin of the Work andreproducing the 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) onan "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,either express or implied, including, without limitation, any warranties orconditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESSFOR A PARTICULAR PURPOSE. You are solely responsible for determiningthe appropriateness of using or redistributing the Work and assume any risksassociated with 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

www.simba.com 38


any and all other commercial damages or losses), even if such Contributor hasbeen advised 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,acceptance of support, warranty, indemnity, or other liability obligations and/orrights consistent with this License. However, in accepting such obligations, Youmay act only on Your own behalf and on Your sole responsibility, not on behalf ofany other Contributor, and only if You agree to indemnify, defend, and hold eachContributor harmless for any liability incurred by, or claims asserted against, suchContributor by reason of your 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):libbsonCopyright © 2013-2015 MongoDB, Inc.MongoDB C DriverCopyright © 2013-2015 MongoDB, Inc.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use thisfile except 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 underthe License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR

www.simba.com 39



CONDITIONS OF ANY KIND, either express or implied. See the License for thespecific language governing permissions and limitations under the License.

www.simba.com 40
