SimbaHubSpotODBCDriverwith SQLConnector...

Simba HubSpot ODBC Driver withSQL Connector

Installation and Configuration Guide

Simba Technologies Inc.

Version 1.1.0

December 23, 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


http://www.simba.com/

About This Guide

PurposeThe Simba HubSpot ODBC Driver with SQL Connector Installation and ConfigurationGuide explains how to install and configure the Simba HubSpot ODBC Driver withSQL Connector. The guide also provides details related to features of the driver.

AudienceThe guide is intended for end users of the Simba HubSpot ODBC Driver, as well asadministrators and developers integrating the driver.

Knowledge PrerequisitesTo use the Simba HubSpot ODBC Driver, the following knowledge is helpful:

l Familiarity with the platform on which you are using the Simba HubSpot ODBCDriver

l Ability to use the data source to which the Simba HubSpot ODBC Driver isconnecting

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

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.

Note:

A text box with a pencil icon indicates a short note appended to a paragraph.

www.simba.com 3


Important:

A text box with an exclamation mark indicates an important comment related to thepreceding paragraph.

www.simba.com 4


Table of Contents

About the SimbaHubSpot ODBC Driver 8

Installing the Driver onWindows 9System Requirements 9Installing Shared Dependencies onWindows 10Installing the Driver onWindows 11Configuring theWindows Registry 12

Configuring the Driver onWindows 13Creating a Data Source Name 13Configuring SSL Verification onWindows 14Exporting a Data Source Name onWindows 16Importing a Data Source Name onWindows 16Configuring Logging Options onWindows 16ConfiguringMemory Usage onWindows 18Encrypting Swap Files onWindows 21

Installing the Driver onmacOS 22System Requirements 22Installing Shared Dependencies onmacOS 22Installing the Driver onmacOS 23

Configuring the ODBC Driver Manager onmacOS 25Specifying ODBC Driver Managers onmacOS 25Specifying the Locations of the Driver Configuration Files 26

Configuring ODBC Connections on a Non-WindowsMachine 27Creating a Data Source Name on a Non-Windows Machine 27Configuring a DSN-less Connection on a Non-Windows Machine 30Configuring SSL Verification on Non-Windows Machines 32Configuring Logging Options on a Non-Windows Machine 33ConfiguringMemory Usage on a Non-Windows Machine 35Encrypting Swap Files on a Non-Windows Machine 37Testing the Connection 37

Using a Connection String 39DSN Connection String Example 39DSN-less Connection String Example 39

www.simba.com 5


Features 42Query Folding 42OAuth 2.0 Authentication 42Stored Procedures 43Memory Manager 43Swap File Encryption 44

Best Practices 45Configure Double-Buffering 45Design Queries that UseQuery Folding 45Design Queries that Use the Top N Command 45

Driver Configuration Options 47Auth_AccessToken 48Auth_Account_Type 48Auth_BaseRedirectUri 49Auth_Client_ID 49Auth_Client_Secret 50Auth_CompletedRedirectUri 50Auth_Expires 50Auth_RefreshToken 51Auth_Scope 51Auth_WindowHeight 51Auth_WindowWidth 52AuthorizationUrl 52Enable Double Buffering 52EncAccessToken 53EncClientSecret 53EncodingType 53Encrypt Swap File 54LogFileCount 54LogFileSize 54LogLevel 55LogPath 55Memory Manager Memory Limit 56Memory Manager Strategy 56Memory Manager Swap Disk Limit 57Memory Manager Threshold Percent 57Proxy Host 58

www.simba.com 6


Proxy Password 58Proxy Port 58Proxy Uid 59Swap File Path 59TrustCertsPath 59Use Encrypted Endpoints 60Use Host Verification 60Use Peer Verification 61Use Windows Proxy Settings 61

Contact Us 62

Third-Party Trademarks 63

Third-Party Licenses 64

www.simba.com 7


About the Simba HubSpot ODBC Driver

The Simba HubSpot ODBC Driver enables Business Intelligence (BI), analytics, andreporting on data that is stored in HubSpot. The driver complies with the ODBC 3.80data standard and adds important functionality such as Unicode, as well as 32- and64-bit support for high-performance computing environments on Windows.

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, see theData Access Standards Glossary: http://www.simba.com/resources/data-access-standards-library. For complete information about the ODBC specification, see theODBC API Reference: http://msdn.microsoft.com/en-us/library/windows/desktop/ms714562(v=vs.85).aspx.

The Installation and Configuration Guide is suitable for users who are looking toaccess data residing within HubSpot from their desktop environment. Applicationdevelopers may also find the information helpful. Refer to your application for detailson connecting via ODBC.

For a complete reference guide to the stored procedures available for the driver anddatabase schema tables used by the driver, see the Simba HubSpot ODBC Driver withSQL Connector Reference Guide.

www.simba.com 8

Installation and Configuration Guide About the Simba HubSpot ODBC Driver

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

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

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

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

Installing the Driver onWindows

The Simba HubSpot ODBC Driver is delivered in a ZIP archive namedSimbaHubSpot_[Version]_Windows.zip, where [Version] is the versionnumber of the driver. In addition to setup files and documentation, this ZIP archivecontains a SimbaHubSpot32_[Version].zip archive and a SimbaHubSpot64_[Version].zip archive, each of which contain the files for the 32-bit and 64-bitdrivers, respectively.

To install the Simba HubSpot ODBC Driver on Windows, you must do the following:

1. Make sure that the required dependencies are installed on your machine. Formore information, see System Requirements on page 9 and Installing SharedDependencies on Windows on page 10.

2. Create the installation directory by extracting the driver files from the ZIP archivesand copying them to the appropriate location, depending on the bitnesses of thedriver and your machine, then link the driver to the required dependencies. Formore information, see Installing the Driver on Windows on page 11.

3. Configure the Windows Registry to recognize the driver and point to thenecessary driver files. For more information, see Configuring the WindowsRegistry on page 12.

System RequirementsInstall the driver on client machines where the application is installed. Each machinethat you install the driver on must meet the following minimum system requirements:

l One of the following operating systems:o Windows Vista, 7, 8, or 10o Windows Server 2008 or later

l 35 MB of available disk spacel Visual C++ Redistributable for Visual Studio 2013 installed (both 32- and 64-bit).You can download the installation packages at https://www.microsoft.com/en-ca/download/details.aspx?id=40784.

In addition, the following libraries must be installed in the Common directory:

l ICU 53.1 or laterl OpenSSL 1.0.1 or laterl RDFODBC 1.3.1 or later

www.simba.com 9

Installation and Configuration Guide Installing the Driver onWindows

https://www.microsoft.com/en-ca/download/details.aspx?id=40784

https://www.microsoft.com/en-ca/download/details.aspx?id=40784

Note:

For information about setting up the Common directory, see Installing SharedDependencies on Windows on page 10.

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

Installing Shared Dependencies on WindowsSome Simba drivers, including the Simba HubSpot ODBC Driver, depend on acommon set of libraries. The drivers share these dependencies from the Commondirectory, which is located parallel to the driver installation directory. Before installingthe driver, make sure that the required libraries are installed in the Common directory.

The libraries are provided with the driver in ZIP archives. The following table lists thelibraries that the Simba HubSpot ODBC Driver requires and the file name of theZIP archive that contains the library:

Required Library Archive Name

ICU 53.1 or later Simba_ICU_[Version]_vs2013.zip

OpenSSL 1.0.1 or later Simba_OpenSSL_[Version]_vs2013.zip

RDFODBC 1.3.1 or later RDFODBC_[Version]_Windows_vs2013.zip

The full path of the Common directory must be one of the following, depending on thebitness of the driver and your machine:

l If you are installing the 32-bit driver on a 64-bit machine, then the shareddependencies must be installed in C:\Program Files(x86)\Simba\Common.

l Otherwise, the shared dependencies must be installed in C:\ProgramFiles\Simba\Common.

To install shared dependencies on Windows:

1. If the Common directory does not already exist, then create it by doing one of thefollowing:

www.simba.com 10


l If you are installing the 32-bit driver on a 64-bit machine, create thedirectory C:\Program Files (x86)\Simba\Common.

l Otherwise, create the directory C:\Program Files\Simba\Common.2. For each dependency that is not already installed, extract the ZIP archive and

then copy the contents from the Common subfolder into the directory from theprevious step.

You can now install and use the Simba HubSpot ODBC Driver.

Installing the Driver on WindowsTo install the driver, create the installation directory for the Simba HubSpot ODBCDriver by extracting the driver files from the ZIP archive and copying them to theappropriate location. Then, link the driver to the required dependencies.

On 64-bit Windows operating systems, you can execute 32- and 64-bit applicationstransparently. However, 64-bit applications must use 64-bit drivers, and 32-bitapplications must use 32-bit drivers. Make sure that you install the version of the driverthat matches the bitness of the client application. You can install both versions of thedriver on the same machine.

Note:

Before installing the driver, make sure that all the dependencies are installed onyour machine. For more information, see "System Requirements" in Installing theDriver on Windows on page 9 and Installing Shared Dependencies on Windowson page 10.

To install the driver on Windows:

1. Create the driver’s installation directory by doing one of the following:l If you are installing the 32-bit driver on a 64-bit machine, create thedirectory C:\Program Files (x86)\Simba\Simba HubSpotODBC Driver.

l Otherwise, create the directory C:\Program Files\Simba\SimbaHubSpot ODBC Driver.

2. Extract the SimbaHubSpot_[Version]_Windows.zip archive into aconvenient temporary location.

3. Depending on whether you are installing the 32-bit or 64-bit driver, do one of thefollowing:

l To install the 32-bit driver, extract the SimbaHubSpot32_[Version].zip archive into a convenient temporary location.

www.simba.com 11


l To install the 64-bit driver, extract the SimbaHubSpot64_[Version].zip archive into a convenient temporary location.

4. Copy the extracted files from the SimbaHubSpot[Bitness]_[Version]subfolder to the installation directory that you created in step 1.

5. Copy the HubSpotODBC.did file from the temporary location in step 2 to the\lib subfolder in the installation directory.

6. In the installation directory, double-click the ImportDependencies.bat file to runit.

The batch file creates the necessary links between the driver and the dependencies inthe Common directory, completing the driver installation process.

Configuring the Windows RegistryTo complete the installation process, run the appropriate .reg file from the driverpackage. This creates registry keys that do the following:

l Define the driver, specifying its location and indicating that it is installed.l Specify driver-wide configuration settings (settings that apply to all connectionsthat use the Simba HubSpot ODBC Driver).

To configure the Windows Registry:

1. In the directory where you extracted the driver package, browse to the setupfolder.

2. Double-click the .reg file that matches the bitness of the driver and yourmachine. For example, if you are installing the 32-bit driver on a 64-bit machine,double-click the Setup-32bitDriverOn64Windows.reg file to run it.

The system returns a message indicating whether the registry keys were createdsuccessfully. If the keys were created successfully, you can now configure aconnection and use the driver to access your HubSpot data.

www.simba.com 12


Configuring the Driver onWindows

Creating a Data Source NameTypically, after installing the Simba HubSpot ODBC Driver, you need to create a DataSource Name (DSN).

Alternatively, for information about DSN-less connections, see Using a ConnectionString on page 39.

To create a Data Source Name:

1. Choose one:

l If you are using Windows 7 or earlier, click Start , then type regedit in theSearch field, and then click regedit.exe in the search results.

l Or, if you are using Windows 8 or later, on the Start screen, type regedit,and then click the regedit search result.

2. Navigate to the appropriate registry key for the bitness of your driver and yourmachine:

l If you are using the 32-bit driver on a 64-bit machine, then browse to thefollowing registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI

l Otherwise, browse to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI

3. Create a subkey for your DSN by doing the following:a. Right-click the ODBC.INI key and then select New > Key.b. Type a name for your DSN and then press Enter.

4. Create the Driver value by doing the following:a. Right-click the DSN subkey and then select New > String Value.b. Type Driver, and then press Enter.c. Right-click the Driver value and then click Modify.d. In the Edit String dialog box, type Simba HubSpot ODBC Driver in the

Value Data field, and then click OK.5. Optionally, repeat the process described in the previous step to create a

Description value where the value data is a description of the DSN.6. Configure authentication by doing one of the following:

l If you already have a valid access token, then create a string value wherethe value name is Auth_AccessToken and the value data is your access token

www.simba.com 13

Installation and Configuration Guide Configuring the Driver onWindows

for authentication.l Or, to provide your HubSpot credentials so that the driver obtains and usesan access token, create the following string values in the DSN subkey:

Value Name Value Data

Auth_BaseRedirectUri

The redirect URL associated with your HubSpot app.

Auth_Account_Type

Your HubSpot account type, which indicates thescopes to use in the access token that the driverretrieves. The supported values aremarketingScopes and nonMarketingScopes.

Auth_Scope (Optional) A comma-separated list of scopes for theaccess token. The scopes that you specify in thissetting take precedence over the scopes specified bythe Auth_Account_Type setting.

Auth_Client_ID The client ID associated with your HubSpot app.

Auth_Client_Secret

The client secret associated with your HubSpot app.

The driver uses these settings to go through an OAuth 2.0 authenticationflow and authenticate your connection to HubSpot. For more information,see OAuth 2.0 Authentication on page 42.

7. Create key values to configure SSL as needed. For more information seeConfiguring SSL Verification on Windows on page 14.

8. Optionally, create additional key values as needed to specify other optionalconnection settings. For detailed information about all the configuration optionssupported by the Simba HubSpot ODBC Driver, see Driver ConfigurationOptions on page 47.

You can now use the DSN in an application to connect to the data store.

Configuring SSL Verification on Windows

Note:

In this documentation, "SSL" indicates both TLS (Transport Layer Security) andSSL (Secure Sockets Layer). The driver uses the TLS/SSL version supported bythe server that you are connecting to, and can support up to TLS 1.2.

www.simba.com 14


When connecting to data stores, by default the Windows version of the Simba HubSpotODBC Driver uses one-way SSL authentication with peer and host verification. Thedriver verifies the identity of the server, and the host name specified in the servercertificate must match the host name of the server that you are connecting to. Tosuccessfully connect to the server, you must either provide the appropriate trustedserver certificate or disable peer verification.

Specifying a Server CertificateThe Windows version of the driver enables peer verification by default. The driver usesthe certificates in the Windows trust store to verify the server. To add a certificate to thetrust store, use the Microsoft Management Console (MMC). For more information, see"Manage Trusted Root Certificates" on Microsoft TechNet:https://technet.microsoft.com/en-us/library/cc754841(v=ws.11).aspx.

Disabling SSL VerificationIf peer verification is not required for your connection, disable peer verification so thatthe driver can connect to the data store. You can also disable host verification andSSL encryption, if necessary.

Note:

It is recommended that you keep SSL enabled if possible. SSL encryption protectsdata and credentials when they are transferred over the network, and providesstronger security than authentiation alone.

To disable SSL verification on Windows:

1. Choose one:

l If you are using Windows 7 or earlier, click Start , then type regedit in theSearch field, and then click regedit.exe in the search results.

l Or, if you are using Windows 8 or later, on the Start screen, type regedit,and then click the regedit search result.

2. Navigate to the subkey for your DSN:l If you are using the 32-bit driver on a 64-bit machine, then browse to thefollowing registry key, where [DSN_Name] is the name of your DSN:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\[DSN_Name]l Otherwise, browse to the following registry key, where [DSN_Name] is thename of your DSN:

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\[DSN_Name]

www.simba.com 15


https://technet.microsoft.com/en-us/library/cc754841(v=ws.11).aspx

3. To disable peer verification so that the driver does not verify the identity of theserver, set the UsePeerVerification value to 0.

4. To disable host verification so that the driver does not require the host name inthe server's certificate to match the host name of the server, set theUseHostVerification value to 0.

5. To disable SSL encryption so that the driver does not connect to the server overSSL, set the UseEncryptedEndpoints value to 0.

Exporting a Data Source Name on WindowsAfter you configure a DSN, you can export it to be used on other machines. When youexport a DSN, all of its configuration settings are saved in a .sdc file. You can thendistribute the .sdc file to other users so that they can import your DSN configurationand use it on their machines.

To export a Data Source Name on Windows:

1. Open the ODBC Data Source Administrator corresponding to the bitness of thedriver, select the DSN, click Configure, and then click Logging Options.

2. Click Export Configuration, specify a name and location for the exported DSN,and then click Save.

Your DSN is saved as a .sdc file in the location that you specified.

Importing a Data Source Name on WindowsYou can import a DSN configuration from a .sdc file and then use those settings toconnect to your data source.

To import a Data Source Name on Windows:

1. Open the ODBC Data Source Administrator corresponding to the bitness of thedriver, select the DSN, click Configure, and then click Logging Options.

2. Click Import Configuration, browse to select the .sdc file that you want toimport the DSN configuration from, and then click Open.

3. Click OK to close the Logging Options dialog box.

The Simba RestSQL ODBC Driver DSN Setup dialog box loads the configurationsettings from the selected .sdc file. You can now save this DSN and use it to connectto your data source.

Configuring Logging Options on WindowsTo help troubleshoot issues, you can enable logging.

www.simba.com 16


Important:

l Only enable logging or tracing long enough to capture an issue. Loggingdecreases performance and can consume a large quantity of disk space.

l Driver-wide configuration settings, such as logging, are applied to all driversthat use the RDFODBC dependency.

Logging is configured through driver-wide settings in the rdf.rdfodbc.ini file,which apply to all connections that use the driver.

To enable driver logging on Windows:

1. Navigate to one of the following directories:l If you are using a 32-bit driver on a 64-bit machine, then go to theC:\Program Files (x86)\Simba\Common\RDFODBC\[LibVersion]\vs[CompilerVersion]\setup directory.

l Otherwise, go to the C:\Program Files\Simba\Common\RDFODBC\[LibVersion]\vs[CompilerVersion]\setup directory.

Where [LibVersion] is the RDFODBC version number and [CompilerVersion] isthe Visual Studio version number.

2. Open the rdf.rdfodbc.ini file in a text editor.3. To specify the level of information to include in the log files, set the LogLevel

property to one of the following numbers:

Logging Level Description

0 Disables all logging.

1 Logs severe error events that lead the driver to abort.

2 Logs error events that might allow the driver to continuerunning.

3 Logs events that might result in an error if action is nottaken.

4 Logs general information that describes the progress ofthe driver.

5 Logs detailed information that is useful for debugging thedriver.

6 Logs all driver activity.

www.simba.com 17


4. Set the LogPath property to the full path to the folder where you want to savelog files.

5. Optionally, set the LogFileSize key to the maximum size of each log file inmegabytes (MB).

Note:

After the maximum file size is reached, the driver creates a new file andcontinues logging.

6. Optionally, set the LogFileCount key to the maximum number of log files tokeep.

Note:

After the maximum number of log files is reached, each time an additionalfile is created, the driver deletes the oldest log file.

7. Save the rdf.rdfodbc.ini file.8. Restart your ODBC application to make sure that the new settings take effect.

The Simba HubSpot ODBC Driver produces a log file namedSimbaHubSpotODBCDriver.log at the location you specify using the LogPathsetting.

To disable driver logging on Windows:




2. Open the rdf.rdfodbc.ini file in a text editor.3. Set the LogLevel property to 0.4. Save the rdf.rdfodbc.ini file.5. Restart your ODBC application to make sure that the new settings take effect.

Configuring Memory Usage on WindowsSome SQL operations, when applied to non-SQL data, require data to be cachedtemporarily before they can be completed. You can configure the Memory Manager

www.simba.com 18


feature in the driver to restrict the amount of RAM or disk space that the driver can useto cache data. For more information, see Memory Manager on page 43.

Important:

l By default, when data is cached as a file on disk, it is stored as unencrypteddata. For information about encrypting this data to prevent security risks, seeEncrypt Swap File on page 54.

l Driver-wide configuration settings, such as the settings for the MemoryManager, are applied to all drivers that use the RDFODBC dependency.

To configure memory usage on Windows:




2. Open the rdf.rdfodbc.ini file in a text editor.3. Set the properties as follows:

Property Value

MemoryManagerMemoryLimit The maximum amount of RAM inmegabytes (MB) that the drivercan use to cache data forSQL operations.

MemoryManagerThresholdPercent The maximum percentage of thememory limit that can be used byan existing operation. Theremaining memory limit isreserved for new operations.

www.simba.com 19


Property Value

MemoryManagerStrategy One of the following numbersspecifying how the driver restrictsRAM usage and managesoperations when more RAM isrequired:

l 1: The driver does not useany disk space to supportSQL operations.

l 2: The driver restricts theamount of RAM that eachoperation can use, anduses swap files to supportoperations if more memoryis required.

l 3: The driver allows the firstSQL operation to consumeas much RAM as necessaryfrom the amounts specifiedby the memory limit andthreshold, while subsequentoperations use theremaining amount.

SwapFilePath The full path to the directorywhere the driver creates swapfiles to temporarily cache data ondisk.

MemoryManagerSwapDiskLimit The maximum total size of all theswap files, in megabytes (MB).

When this option is set to 0, thereis no limit to the size of the swapfiles.

For more information about each of these settings, including recommendationsfor setting the MemoryManagerStrategy property, see .

4. Save the rdf.rdfodbc.ini file.

www.simba.com 20


Encrypting Swap Files on WindowsTo keep all data as secure as possible, the Simba HubSpot ODBC Driver allows youto encrypt the swap file content.

Important:

l Enabling swap file encryption can significantly decrease performance. Onlyenable swap file encryption in situations where it is required.

l Driver-wide configuration settings, such as swap file encryption, are appliedto all drivers that use the RDFODBC dependency.

To enable swap file encryption on Windows:




2. Open the rdf.rdfodbc.ini file in a text editor.3. Set the EncryptSwapFile property to 1.4. Save the rdf.rdfodbc.ini file.

www.simba.com 21


Installing the Driver on macOS

The Simba HubSpot ODBC Driver is delivered in a TAR archive namedSimbaHubSpotODBC_[Version]-OSX.tar.gz, where [Version] is the versionnumber of the driver.

To install the Simba HubSpot ODBC Driver, you must do the following:

1. Make sure that the required dependencies are installed on your machine. Formore information, see System Requirements on page 22 and Installing SharedDependencies on macOS on page 22.

2. Create the installation directory by extracting the driver files from the TARarchives and copying them to the appropriate location. Then link the driver to therequired dependencies. For more information, see Installing the Driver onmacOS on page 23.

System RequirementsInstall the driver on client machines where the application is installed. Each machinethat you install the driver on must meet the following minimum system requirements:

l macOS version 10.9, 10.10, or 10.11l 35 MB of available disk spacel iODBC 3.52.7 or later

In addition, the following libraries must be installed in the Common directory:

l ICU 53.1 or laterl OpenSSL 1.0.1 or laterl RDFODBC 1.3.1 or later

Note:

For information about setting up the Common directory, see Installing SharedDependencies on macOS on page 22.

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

Installing Shared Dependencies on macOSSome Simba drivers, including the Simba HubSpot ODBC Driver, depend on acommon set of libraries. Before installing the driver, make sure that these libraries areinstalled in the Common directory.

www.simba.com 22

Installation and Configuration Guide Installing the Driver onmacOS

The Common directory must be located parallel to the driver installation directory. Forexample, if your driver is installed in /Library/simba/hubspotodbc, the Commondirectory must be located at /Library/simba/Common.

The libraries are provided with the driver in TAR archives. The following table lists thelibraries that the Simba HubSpot ODBC Driver requires and the file name of the TARarchive that contains the library:

Required Library Archive Name

ICU 53.1 or later Simba_ICU_[Version]_xcode5_1.tar.gz

OpenSSL 1.0.1 or later Simba_OpenSSL_[Version]_xcode5_1.tar.gz

RDFODBC 1.3.1 or later RDFODBC_[Version]_OSX_xcode5_1.tar.gz

To install shared dependencies on macOS:

1. If the Common directory does not already exist in the directory where you want toinstall the driver, then create it.

2. For each dependency that is not already installed, extract the TAR archive andthen copy the contents from the Common subfolder into the directory from theprevious step.

You can now install and use the Simba HubSpot ODBC Driver.

Installing the Driver on macOSTo install the driver, create the installation directory for the Simba HubSpot ODBCDriver by extracting the driver files from the TAR archive and copying them to theappropriate location. Then, link the driver to the required dependencies.

Note:

Before installing the driver, make sure that all the dependencies are installed onyour machine. For more information, see "System Requirements" in Installing theDriver on macOS on page 22 and Installing Shared Dependencies on macOS onpage 22.

www.simba.com 23


To install the driver on macOS:

1. Create the driver’s installation directory. The recommended location is/Library/simba/hubspotodbc.

2. Extract the SimbaHubSpotODBC_[Version]-OSX.tar.gz archive into aconvenient temporary location.

3. Extract the SimbaHubSpotODBC_[Version].tar.gz archive into aconvenient temporary location.

4. Copy the extracted files from the SimbaHubSpotODBC_[Version] subfolderto the installation directory that you created in step 1.

5. Copy the HubSpotODBC.did file from the temporary location in step 2 to the/lib subfolder in the installation directory.

6. In the installation directory, double-click the ImportDependencies.sh file to runit.

The batch file creates the necessary links between the driver and the dependencies inthe Common directory, completing the driver installation.

www.simba.com 24


Configuring the ODBC Driver Manager on macOS

To make sure that the ODBC driver manager on your machine is configured to workwith the Simba HubSpot ODBC Driver, do the following:

l Make sure that your machine uses the correct ODBC driver manager by settingthe library path environment variable. For more information, see SpecifyingODBC Driver Managers on macOS on page 25.

l If the driver configuration files are not stored in the default locations, then makesure that the ODBC driver manager locates and uses those files by settingenvironment variables. For more information, see Specifying the Locations of theDriver Configuration Files on page 26.

After configuring the ODBC driver manager, you can configure a connection andaccess your data store through the driver. For more information, see ConfiguringODBC Connections on a Non-Windows Machine on page 27.

Specifying ODBC Driver Managers on macOSYou need to make sure that your machine uses the correct ODBC driver manager toload the driver. To do this, set the library path environment variable.

If you are using a macOS machine, then set the DYLD_LIBRARY_PATH environmentvariable to include the paths to the ODBC driver manager libraries. For example, if thelibraries are installed in /usr/local/lib, then run the following command to setDYLD_LIBRARY_PATH for the current user session:

export DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:/usr/local/lib

For information about setting an environment variable permanently, refer to the macOSshell documentation.

www.simba.com 25

Installation and Configuration Guide Configuring the ODBC Driver Manager onmacOS

Specifying the Locations of the Driver ConfigurationFilesBy default, ODBC driver managers are configured to use hidden versions of theodbc.ini and odbcinst.ini configuration files (named .odbc.ini and.odbcinst.ini) located in the home directory. If you want to store theseconfiguration files in different locations, then you must set environment variables toindicate the locations of these files:

l Set ODBCINI to point to your odbc.ini file.l Set ODBCINSTINI to point to your odbcinst.ini file.

For example, if your odbc.ini file is located in /etc and your odbcinst.ini fileis located in /usr/local/odbc, then set the environment variables as follows:

export ODBCINI=/etc/odbc.iniexport ODBCINSTINI=/usr/local/odbc/odbcinst.ini

www.simba.com 26

Installation and Configuration Guide Configuring the ODBC Driver Manager onmacOS

ConfiguringODBC Connections on a Non-WindowsMachine

The following sections describe how to configure ODBC connections when using theSimba HubSpot ODBC Driver on non-Windows platforms:

l Creating a Data Source Name on a Non-Windows Machine on page 27l Configuring a DSN-less Connection on a Non-Windows Machine on page 30l Configuring SSL Verification on Non-Windows Machines on page 32l Configuring Logging Options on a Non-Windows Machine on page 33l Configuring Memory Usage on a Non-Windows Machine on page 35l Encrypting Swap Files on a Non-Windows Machine on page 37l Testing the Connection on page 37

Creating a Data Source Name on a Non-WindowsMachineWhen connecting to your data store using a DSN, you only need to configure theodbc.ini file. Set the properties in the odbc.ini file to create a DSN that specifiesthe connection information for your data store. For information about configuring aDSN-less connection instead, see Configuring a DSN-less Connection on a Non-Windows Machine on page 30.

If your machine is already configured to use an existing odbc.ini file, then updatethat file by adding the settings described below. Otherwise, copy the odbc.ini filefrom the Setup subfolder in the driver installation directory to the home directory, andthen update the file as described below.

To create a Data Source Name on a non-Windows machine:

1. In a text editor, open the odbc.ini configuration file.

Note:

When using a hidden copy of the odbc.ini file, you may remove theperiod (.) from the start of the file name to make it visible while editing thefile.

2. In the [ODBC Data Sources] section, add a new entry by typing a name forthe DSN, an equal sign (=), and then the name of the driver.

For example:

www.simba.com 27

Installation and Configuration Guide Configuring ODBC Connections on a Non-Windows Machine

[ODBC Data Sources]Sample DSN=Simba HubSpot ODBC Driver

3. Create a section that has the same name as your DSN, and then specifyconfiguration options as key-value pairs in the section:a. Set the Driver property to the full path of the driver library file that

matches the bitness of the application.

For example:

Driver=/Library/simba/hubspotodbc/lib/libhubspotodbc_sbu.dylib

b. Configure authentication by doing one of the following:l If you already have a valid access token, then set the Auth_AccessToken property to your access token for authentication.

For example:

Auth_AccessToken=1jt9Pcyq8pr3lvu143pfl4r86

l Or, to provide your HubSpot credentials so that the driver obtains anduses an access token, set the following properties:

Property Value

Auth_BaseRedirectUri The redirect URL associatedwith your HubSpot app.

Auth_Client_ID The client ID associated withyour HubSpot app.

Auth_Client_Secret The client secret associatedwith your HubSpot app.

Auth_Account_Type Your HubSpot account type,which indicates the scopes touse in the access token that thedriver retrieves. The supportedvalues aremarketingScopes andnonMarketingScopes.

www.simba.com 28


Property Value

Auth_Scope (Optional) A comma-separatedlist of scopes for the accesstoken. The scopes that youspecify in this setting takeprecedence over the scopesspecified by the Auth_Account_Type setting.

For example:

Auth_BaseRedirectUri=https://www.hubspot.comAuth_Client_ID=f145kn9Pcyq9pr4lvumdapfl4riveAuth_Client_Secret=45kn9Pcyq9pr4lvu123pfl4r57Auth_Account_Type=marketingScopes

The driver uses these settings to go through an OAuth 2.0authentication flow and authenticate your connection to HubSpot. Formore information, see OAuth 2.0 Authentication on page 42.

c. Configure SSL as needed. For more information, see ConfiguringSSL Verification on Non-Windows Machines on page 32.

d. Optionally, set additional key-value pairs as needed to specify otheroptional connection settings. For detailed information about all theconfiguration options supported by the Simba HubSpot ODBC Driver, seeDriver Configuration Options on page 47.

4. Save the odbc.ini configuration file.

Note:

If you are storing this file in its default location in the home directory, thenprefix the file name with a period (.) so that the file becomes hidden. If youare storing this file in another location, then save it as a non-hidden file(without the prefix), and make sure that the ODBCINI environment variablespecifies the location. For more information, see Specifying the Locations ofthe Driver Configuration Files on page 26.

For example, the following is an odbc.ini configuration file containing a DSN thatconnects to HubSpot using an access token:

[ODBC Data Sources]Sample DSN=Simba HubSpot ODBC Driver[Sample DSN]

www.simba.com 29


Driver=/Library/simba/hubspotodbc/lib/libhubspotodbc_sbu.dylibAuth_BaseRedirectUri=https://www.hubspot.comAuth_Client_ID=f145kn9Pcyq9pr4lvumdapfl4riveAuth_Client_Secret=45kn9Pcyq9pr4lvu123pfl4r57Auth_AccountType=marketingScopes

You can now use the DSN in an application to connect to the data store.

Configuring a DSN-less Connection on a Non-Windows MachineTo connect to your data store through a DSN-less connection, you need to define thedriver in the odbcinst.ini file and then provide a DSN-less connection string inyour application.

If your machine is already configured to use an existing odbcinst.ini file, thenupdate that file by adding the settings described below. Otherwise, copy theodbcinst.ini file from the Setup subfolder in the driver installation directory to thehome directory, and then update the file as described below.

To define a driver on a non-Windows machine:

1. In a text editor, open the odbcinst.ini configuration file.

Note:

When using a hidden copy of the odbcinst.ini file, you may remove theperiod (.) from the start of the file name to make it visible while editing thefile.

2. In the [ODBC Drivers] section, add a new entry by typing a name for thedriver, an equal sign (=), and then Installed.

For example:

[ODBC Drivers]Simba HubSpot ODBC Driver=Installed

3. Create a section that has the same name as the driver (as specified in theprevious step), and then specify the following configuration options as key-valuepairs in the section:a. Set the Driver property to the full path of the driver library file that

matches the bitness of the application.

www.simba.com 30


For example:

Driver=/Library/simba/hubspotodbc/lib/libhubspotodbc_sbu.dylib

b. Optionally, set the Description property to a description of the driver.

For example:

Description=Simba HubSpot ODBC Driver

4. Save the odbcinst.ini configuration file.

Note:

If you are storing this file in its default location in the home directory, thenprefix the file name with a period (.) so that the file becomes hidden. If youare storing this file in another location, then save it as a non-hidden file(without the prefix), and make sure that the ODBCINSTINI environmentvariable specifies the full path of the file. For more information, seeSpecifying the Locations of the Driver Configuration Files on page 26.

For example, the following is an odbcinst.ini configuration file:

[ODBC Drivers]Simba HubSpot ODBC Driver=Installed[Simba HubSpot ODBC Driver]Description=Simba HubSpot ODBC DriverDriver=/Library/simba/hubspotodbc/lib/libhubspotodbc_sbu.dylib

You can now connect to your data store by providing your application with aconnection string where the Driver property is set to the driver name specified in theodbcinst.ini file, and all the other necessary connection properties are also set.For more information, see "DSN-less Connection String Examples" in Using aConnection String on page 39.

For instructions about configuring SSL connections, see Configuring SSL Verificationon Non-Windows Machines on page 32.

For detailed information about all the connection properties that the driver supports,see Driver Configuration Options on page 47.

www.simba.com 31


Configuring SSL Verification on Non-WindowsMachines

Note:

In this documentation, "SSL" indicates both TLS (Transport Layer Security) andSSL (Secure Sockets Layer). The driver uses the TLS/SSL version supported bythe server that you are connecting to, and can support up to TLS 1.2.

When connecting to data stores, by default the non-Windows version of the driverSimba HubSpot ODBC Driver uses SSL encryption but does not use peer or hostverification. You can enable peer verification so that the driver verifies the identity ofthe server, and enable host verification so that the driver requires the host name in theserver certificate to match the host name of the server that you are connecting to.

You can set the connection properties described below in a connection string or in aDSN (in the odbc.ini file). Settings in the connection string take precedence oversettings in the DSN.

Configuring Host and Peer Verification

To configure host and peer verification:

1. To enable peer verification so that the driver verifies the identity of the server, dothe following:a. Set the UsePeerVerification property to 1.b. Set the TrustCertsPath property to the full path and name of a .pem

file containing the trusted CA certificates for verifying the server.2. To enable host verification so that the driver requires the host name in the

server's certificate to match the host name of the server, set theUseHostVerification property to 1.

Disabling SSL EncryptionIf the data store that you are connecting to does not support SSL encryption, disable itso that the driver can connect to the data store.

Note:

It is recommended that you keep SSL enabled if possible. SSL encryption protectsdata and credentials when they are transferred over the network, and providesstronger security than authentiation alone.

www.simba.com 32


To disable SSL verification on a non-Windows machine:

Set the UseEncryptedEndpoints property to 0.

Configuring Logging Options on a Non-WindowsMachineTo help troubleshoot issues, you can enable logging in the driver.

Important:

l Only enable logging or tracing long enough to capture an issue. Loggingdecreases performance and can consume a large quantity of disk space.

l Driver-wide configuration settings, such as logging, are applied to all driversthat use the RDFODBC dependency.

Logging is configured through driver-wide settings in the rdf.rdfodbc.ini file,which apply to all connections that use the driver.

To enable logging on a non-Windows machine:

1. Navigate to the /Library/simba/Common/RDFODBC/[LibVersion]/xcode[CompilerVersion]/setup directory, where[LibVersion] is the RDFODBC version number and [CompilerVersion] is theXcode version number.

2. Open the rdf.rdfodbc.ini configuration file in a text editor.3. To specify the level of information to include in log files, set the LogLevel

property to one of the following numbers:

LogLevel Value Description

0 Disables all logging.

1 Logs severe error events that lead the driver to abort.

2 Logs error events that might allow the driver to continuerunning.

3 Logs events that might result in an error if action is nottaken.

4 Logs general information that describes the progress ofthe driver.

www.simba.com 33


LogLevel Value Description

5 Logs detailed information that is useful for debugging thedriver.

6 Logs all driver activity.

4. Set the LogPath property to the full path to the folder where you want to savelog files.

5. Set the LogFileCount property to the maximum number of log files to keep.

Note:

After the maximum number of log files is reached, each time an additionalfile is created, the driver deletes the oldest log file.

6. Set the LogFileSize property to the maximum size of each log file inmegabytes (MB).

Note:

After the maximum file size is reached, the driver creates a new file andcontinues logging.

7. Save the rdf.rdfodbc.ini configuration file.8. Restart your ODBC application to make sure that the new settings take effect.

The Simba HubSpot ODBC Driver produces a log file namedSimbaHubSpotODBCDriver.log at the location you specify using the LogPathsetting.

To disable logging on a non-Windows machine:


2. Open the rdf.rdfodbc.ini configuration file in a text editor.3. Set the LogLevel property to 0.4. Save the rdf.rdfodbc.ini configuration file.5. Restart your ODBC application to make sure that the new settings take effect.

www.simba.com 34


Configuring Memory Usage on a Non-WindowsMachineSome SQL operations, when applied to non-SQL data, require data to be cachedtemporarily before they can be completed. You can configure the Memory Managerfeature in the driver to restrict the amount of RAM or disk space that the driver can useto cache data. For more information, see Memory Manager on page 43.

Important:

l By default, when data is cached as a file on disk, it is stored as unencrypteddata. For information about encrypting this data to prevent security risks, seeEncrypting Swap Files on a Non-Windows Machine on page 37.

l Driver-wide configuration settings, such as the settings for the MemoryManager, are applied to all drivers that use the RDFODBC dependency.

To configure memory usage on a non-Windows machine:


2. Open the rdf.rdfodbc.ini configuration file in a text editor.3. Set the properties as follows:

Property Value

MemoryManagerMemoryLimit The maximum amount of RAM inmegabytes (MB) that the drivercan use to cache data forSQL operations.

MemoryManagerThresholdPercent The maximum percentage of thememory limit that can be used byan existing operation. Theremaining memory limit isreserved for new operations.

www.simba.com 35


Property Value

MemoryManagerStrategy One of the following numbersspecifying how the driver restrictsRAM usage and managesoperations when more RAM isrequired:

l 1: The driver does not useany disk space to supportSQL operations.

l 2: The driver restricts theamount of RAM that eachoperation can use, anduses swap files to supportoperations if more memoryis required.

l 3: The driver allows the firstSQL operation to consumeas much RAM as necessaryfrom the amounts specifiedby the memory limit andthreshold, while subsequentoperations use theremaining amount.

SwapFilePath The full path to the directorywhere the driver creates swapfiles to temporarily cache data ondisk.

MemoryManagerSwapDiskLimit The maximum total size of all theswap files, in megabytes (MB).

When this option is set to 0, thereis no limit to the size of the swapfiles.

For more information about each of these settings, including recommendationsfor setting the MemoryManagerStrategy property, see .

4. Save the rdf.rdfodbc.ini file.

www.simba.com 36


Encrypting Swap Files on a Non-Windows MachineTo keep all data as secure as possible, the Simba HubSpot ODBC Driver allows youto encrypt the swap file content.

Important:

l Enabling swap file encryption can significantly decrease performance. Onlyenable swap file encryption in situations where it is required.

l Driver-wide configuration settings, such as swap file encryption, are appliedto all drivers that use the RDFODBC dependency.

To enable swap file encryption on a non-Windows machine:


2. Open the rdf.rdfodbc.ini configuration file in a text editor.3. Set the EncryptSwapFile property to 1.4. Save the rdf.rdfodbc.ini file.

Testing the ConnectionTo test the connection, you can use an ODBC-enabled client application. For a basicconnection test, you can also use the test utilities that are packaged with your drivermanager installation. For example, the iODBC driver manager includes simple utilitiescalled iodbctest and iodbctestw.

Using the iODBC Driver ManagerYou can use the iodbctest and iodbctestw utilities to establish a test connection withyour driver. Use iodbctest to test how your driver works with an ANSI application, oruse iodbctestw to test how your driver works with a Unicode application.

Note:

There are 32-bit and 64-bit installations of the iODBC driver manager available. Ifyou have only one or the other installed, then the appropriate version of iodbctest(or iodbctestw) is available. However, if you have both 32- and 64-bit versionsinstalled, then you need to make sure that you are running the version from thecorrect installation directory.

For more information about using the iODBC driver manager, see http://www.iodbc.org.

www.simba.com 37


http://www.iodbc.org/

To test your connection using the iODBC driver manager:

1. Run iodbctest or iodbctestw.2. Optionally, if you do not remember the DSN, then type a question mark (?) to see

a list of available DSNs.3. Type an ODBC connection string using the following format, specifying

additional connection attributes as needed:

DSN=[DataSourceName];[Key]=[Value]

[DataSourceName] is the DSN that you are using for the connection.[Key] isany connection attribute that is not already specified as a configuration key in theDSN, and [Value] is the value for the attribute. Add key-value pairs to theconnection string as needed, separating each pair with a semicolon (;).

If the connection is successful, then the SQL> prompt appears.

Note:

For information about the connection attributes that are available, see DriverConfiguration Options on page 47.

www.simba.com 38


Using a Connection String

For some applications, you might need to use a connection string to connect to yourdata source. For detailed information about how to use a connection string in an ODBCapplication, refer to the documentation for the application that you are using.

The connection strings in the following sections are examples showing the minimumset of connection attributes that you must specify to successfully connect to the datasource. Depending on the configuration of the data source and the type of connectionyou are working with, you might need to specify additional connection attributes. Fordetailed information about all the attributes that you can use in the connection string,see Driver Configuration Options on page 47.

DSN Connection String ExampleThe following is an example of a connection string for a connection that uses a DSN:

DSN=[DataSourceName]

[DataSourceName] is the DSN that you are using for the connection.

You can set additional configuration options by appending key-value pairs to theconnection string. Configuration options that are passed in using a connection stringtake precedence over configuration options that are set in the DSN.

DSN-less Connection String ExampleSome applications provide support for connecting to a data source using a driverwithout a DSN. To connect to a data source without using a DSN, use a connectionstring instead.

The placeholders in the examples are defined as follows, in alphabetical order:

l [RedirectURL] is the redirect URL associated with your HubSpot app.l [YourAccessToken] is your access token for authenticating to HubSpot.l [YourAccountType] is your HubSpot account type, which indicates the scopes touse in the access token that the driver retrieves. The supported values aremarketingScopes and nonMarketingScopes.

l [YourClientID] is the client ID associated with your HubSpot app.l [YourClientSecret] is the client secret associated with your HubSpot app.

www.simba.com 39

Installation and Configuration Guide Using a Connection String

Connecting to HubSpot Using an Access TokenThe following is the format of a DSN-less connection string for connecting to HubSpotusing an access token:

Driver=Simba HubSpot ODBC Driver;Auth_AccessToken=[YourAccessToken]

For example:

Driver=Simba HubSpot ODBC Driver;Auth_AccessToken=a25c7cfd-3621-4f94-a79d-7b308f2b19f2

Note:

If the server does not support HTTPS connections or SSL verification, then youmust disable those features by setting additional properties in your connectionstring. For more information, see Configuring SSL Verification on Windows onpage 14 or Configuring SSL Verification on Non-Windows Machines on page 32.

Connecting to HubSpot Using Your HubSpot CredentialsThe following is the format of a DSN-less connection string for connecting to HubSpotusing your HubSpot credentials. The driver initiates an OAuth 2.0 authentication flowbased on your credentials and then uses the retrieved access token to authenticate theconnection.

Driver=Simba HubSpot ODBC Driver;Auth_Client_ID=[YourClientId];Auth_Client_Secret=[YourClientSecret];Auth_Account_Type=[YourAccountType];Auth_BaseRedirectUri=[RedirectURL]

For example:

Driver=Simba HubSpot ODBC Driver;Auth_Client_ID=11b5516f-1322-11e6-9653-93a39db85acf;Auth_Client_Secret=abCD+E1f2Gxhi3J4klmN/OP5QrSTuvwXYzabcdEF;Auth_Account_Type=marketingScopes;Auth_BaseRedirectUri=https://www.hubspot.com

www.simba.com 40


Note:

If the server does not support HTTPS connections or SSL verification, then youmust disable those features by setting additional properties in your connectionstring. For more information, see Configuring SSL Verification on Windows onpage 14 or Configuring SSL Verification on Non-Windows Machines on page 32.

www.simba.com 41


Features

For more information on the features of the Simba HubSpot ODBC Driver, see thefollowing:

l Query Folding on page 42l OAuth 2.0 Authentication on page 42l Stored Procedures on page 43l Memory Manager on page 43l Swap File Encryption on page 44

Query FoldingUsing query folding, the driver can delegate the processing of certain operations to theserver instead of performing them locally on the client machine. The Simba HubSpotODBC Driver supports query folding for specific columns. When you run a query thatfilters on columns for which folding is supported, the driver attempts to optimize driverperformance by delegating the comparison operation to the server.

For information about the columns that support query folding and examples of how todesign queries that make use of query folding, see "Design Queries that Use QueryFolding" in Best Practices on page 45.

OAuth 2.0 AuthenticationThe Simba HubSpot ODBC Driver uses the OAuth 2.0 protocol for authentication andauthorization. You can authenticate your connection by specifying an access token, orby specifying your HubSpot credentials so that the driver retrieves and uses thecorresponding access token.

When you connect using your HubSpot credentials, the driver initiates an OAuth 2.0authentication flow using SQLBrowseConnect as described below.

1. The application submits a request to the driver with the Driver, Auth_Type,Auth_Client_ID, Auth_Client_Secret, Auth_Account_Type, andAuth_BaseRedirectUri parameters.

2. The driver returns the AuthorizationURL parameter, and requests theCompletedRedirectUri parameter.

3. The application launches the authorization URL in a browser.4. The user authenticates at the authorization URL, and the browser is redirected to

the completed redirect URI.

www.simba.com 42

Installation and Configuration Guide Features

5. The application submits the Auth_CompletedRedirectUri and theAuthorizationURL parameters to the driver.

6. The driver uses information from the Auth_CompletedRedirectUri toretrieve an access token, a refresh token, and an expiration time from the datasource, and then returns them to the application.

7. The application submits the Auth_AccessToken, Auth_RefreshToken, andAuth_Expires parameters to the driver.

Stored ProceduresThe Simba HubSpot ODBC Driver provides stored procedures to optimizeperformance when working with HubSpot data. These stored procedures enable you towork with by calling a single stored procedure instead of designing and executingmultiple query statements.

For detailed information about the stored procedures that the driver supports, see theSimba HubSpot ODBC Driver with SQL Connector Reference Guide.

Memory ManagerWhen executing SQL operations on non-SQL data, the driver often needs to cache thedata temporarily before it can complete the operation. The Memory Manager feature inthe driver allows you to manage the amount of RAM or disk space that the driver canuse to cache data.

Some operations require data to be cached temporarily before they can be completed.For example, when the driver executes a query that contains an ORDER BY clause,the driver caches the retrieved data, sorts the data, and then returns the sorted data asa result set. The cache is then cleared.

You can specify the maximum amount of RAM that the driver can use to support allconcurrent operations. You can also reserve a portion of that RAM for new operations,to ensure that the RAM is not completely consumed by an existing operation. Typically,if an operation or set of operations requires more RAM than the allotted amount, thedriver moves some of the cached data into temporary files called "swap files" in orderto free up memory and complete the operation or operations. You can specify themaximum amount of disk space that can be consumed by swap files, or configure thedriver to stop the operation instead of moving data to disk.

For information about how to configure the Memory Manager in the driver, seeConfiguring Memory Usage on Windows on page 18.

www.simba.com 43


Swap File EncryptionSwap files are temporary data files that are created by the driver during certainoperations. Swap files are deleted once the operation that created them is complete.However, if the application that uses the driver terminates unexpectedly, the swap filesmay remain on the disk. In addition, it is possible for the swap files to be accessedwhile they are in use.

By default, swap files are stored as unencrypted data. This allows for greatly increasedperformance, but may be considered a security risk in certain environments.

To keep your data as secure as possible, the Simba HubSpot ODBC Driver allows youto encrypt the swap file content. For information about how to configure swap fileencryption, see Encrypting Swap Files on Windows on page 21.

Important:

Enabling swap file encryption can significantly decrease performance. Only enableswap file encryption in situations where it is required.

www.simba.com 44


Best Practices

The following are some guidelines and recommendations that can help you optimizedriver performance.

Configure Double-BufferingYou can enable double-buffering to improve performance in the driver. Double-buffering increases the responsiveness of the driver by enabling it to prefetch datawhen executing queries. However, when double-buffering is enabled, the driver mightconsume more memory and CPU time.

By default, double-buffering is enabled. To disable double-buffering, set theEnableDoubleBuffer key in your DSN or connection string to 0.

Design Queries that Use Query FoldingThe Simba HubSpot ODBC Driver supports query folding for certain columns. Queryfolding is a feature that enables the driver to delegate a comparison operation so that itis processed on the server instead of the client. To optimize driver performance, designyour queries to filter on columns for which folding is supported.

When possible, the only columns used in WHERE clauses should be columns thatsupport query folding. Consider using SELECT TOP N statements in situations whereyou cannot use a WHERE clause with these columns.

If you use a WHERE clause that uses any columns that do not support query folding,the driver requests all data from the specified table, and then discards the unnecessarydata. This may require additional API calls that move to the next page to retrieveadditional data.

For a list of foldable columns in each table in the schema, see the SimbaHubSpotReference Guide.

Design Queries that Use the Top N CommandIf query folding is not supported in the table that you need to query, you can optimizedriver performance by designing queries that use the Top N command.

Normally, when you execute a query that filters on a column that is not foldable, thedriver retrieves all the data and then filters the data to return the appropriate result set.This process can be time-consuming and cause the driver to invoke many API calls. Ifyou execute a query using the Top N command, then the driver retrieves only the

www.simba.com 45

Installation and Configuration Guide Best Practices

specified data, and returns additional data only when you make an API call to retrievethe next page of data.

www.simba.com 46

Installation and Configuration Guide Best Practices

Driver Configuration Options

Driver Configuration Options lists the configuration options available in the SimbaHubSpot ODBC Driver alphabetically by key name.

Most of these options can be specified in a DSN or in a connection string, and applyonly to the specific connection for which they are set. If the same option is configured inboth the DSN and the connection string, then the setting in the connection string takesprecedence.

The configuration options that control the Logging, Memory Manager, and Swap FileEncryption features are driver-wide configuration options, which apply to allconnections that use the Simba HubSpot ODBC Driver. These options are specified inthe rdf.rdfodbc.ini configuration file instead of the DSN or connection string. Inaddition, these settings are applied to all drivers that use the RDFODBC dependency.

For detailed information about each driver configuration option, see the followingsections.

l Auth_AccessToken on page 48l Auth_Account_Type on page 48l Auth_Client_ID on page 49l Auth_Client_Secret on page 50l Auth_CompletedRedirectUri onpage 50

l Auth_Expires on page 50l Auth_RefreshToken on page 51l Auth_Scope on page 51l Auth_WindowHeight on page 51l Auth_WindowWidth on page 52l Enable Double Buffering onpage 52

l EncAccessToken on page 53l EncClientSecret on page 53l EncodingType on page 53l Encrypt Swap File on page 54l LogFileCount on page 54l LogFileSize on page 54l LogLevel on page 55

l Memory Manager Memory Limit onpage 56

l Memory Manager Strategy on page56

l Memory Manager Swap Disk Limiton page 57

l Memory Manager Threshold Percenton page 57

l Proxy Host on page 58l Proxy Password on page 58l Proxy Port on page 58l Proxy Uid on page 59l Swap File Path on page 59l TrustCertsPath on page 59l Use Encrypted Endpoints on page60

l Use Host Verification on page 60l Use Peer Verification on page 61l Use Windows Proxy Settings onpage 61

www.simba.com 47

Installation and Configuration Guide Driver ConfigurationOptions

l LogPath on page 55

Auth_AccessToken

Key Name Default Value Required

Auth_AccessToken None Yes, ifEncAccessToken is notset and the driver is notconfigured to go through

an OAuth 2.0authentication flow.

DescriptionThe access token for OAuth 2.0 authentication.

If Auth_AccessToken and EncAccessToken are both set, the driver uses Auth_AccessToken. For more information, see EncAccessToken on page 53.

Auth_Account_Type


Auth_Account_Type None Yes, if the driver isconfigured to go through

an OAuth 2.0authentication flow.

DescriptionYour HubSpot account type, which indicates the scopes to use in the OAuth accesstoken that the driver retrieves.

l marketingScopes: Retrieve and use an access token with the OAuth scopesthat are associated with marketing accounts.

l nonMarketingScopes: Retrieve and use an access token with the OAuthscopes that are associated with non-marketing accounts.

www.simba.com 48


Note:

You can override this setting and specify a custom list of scopes by using theAuth_Scope setting. For more information, see Auth_Scope on page 51.




None Yes, if configuring thedriver to go through anOAuth 2.0 authentication

flow.

DescriptionThe redirect URL associated with your HubSpot app.

Auth_Client_ID


Auth_Client_ID None Yes, if configuring thedriver to go through anOAuth 2.0 authentication

flow.

DescriptionThe client ID associated with your HubSpot app.

www.simba.com 49


Auth_Client_Secret


Auth_Client_Secret None Yes, if configuring thedriver to go through anOAuth 2.0 authentication

flow andEncClientSecret is

not set.

DescriptionThe client secret associated with your HubSpot application.

If both Auth_Client_Secret and EncClientSecret (see EncClientSecret onpage 53) are set, the driver uses Auth_Client_Secret.

Auth_CompletedRedirectUri


Auth_CompletedRedirectUri

None No

DescriptionThe OAuth 2.0 completed redirect URI, which is used to generate the access tokenand the refresh token.

Auth_Expires


Auth_Expires None No

DescriptionThe expiration time for the OAuth 2.0 access token, specified in Unix time format.When the access token expires, the driver uses the refresh token to obtain another

www.simba.com 50


valid access token.

Auth_RefreshToken


Auth_RefreshToken None No

DescriptionThe OAuth 2.0 refresh token for connection.

Auth_Scope


Auth_Scope None No

DescriptionA comma-separated list of OAuth scopes for the access token.

Note:

This setting takes precedence over the Auth_Account_Type setting. For moreinformation, see Auth_Account_Type on page 48.

Auth_WindowHeight


Auth_WindowHeight None (constructed bySQLBrowseConnect)

No

DescriptionThe suggested window height for the login/authorization page for OAuth.

www.simba.com 51


Auth_WindowWidth


Auth_WindowWidth None (constructed bySQLBrowseConnect)

No

DescriptionThe suggested window width for the login/authorization page for OAuth.

AuthorizationUrl


AuthorizationUrl None (constructed bySQLBrowseConnect)

No

DescriptionThe OAuth 2.0 authorization URL, which is used to generate the access token and therefresh token.

Enable Double Buffering


EnableDoubleBuffer Enabled (1) No

DescriptionThis option specifies whether the driver retrieves the data using double-buffering.

l Enabled (1): The driver retrieves the data using double-buffering.l Disabled (0): The driver retrieves the data using single-buffering.

www.simba.com 52


EncAccessToken


EncAccessToken None Yes, if Auth_AccessToken is not set.

DescriptionAn encrypted version of the access token for OAuth authentication.

If EncAccessToken and Auth_AccessToken are both set, the driver uses Auth_AccessToken. For more information, see Auth_AccessToken on page 48

EncClientSecret


EncClientSecret None No

DescriptionIf both Auth_Client_Secret (see Auth_Client_Secret on page 50) andEncClientSecret are set, the driver uses Auth_Client_Secret.

EncodingType


EncodingType NULL No

DescriptionThis option specifies the compression encoding method to use. Compressing yourdata can improve driver performance by improving the rate at which data is passedbetween the driver and the data store.

l OFF: The data is not compressed.l NULL: The driver chooses a supported compression method that bestcompresses the data.

www.simba.com 53


Encrypt Swap File


EncryptSwapFile 0 No

DescriptionThis option specifies whether the swap file is encrypted.

Important:

Enabling swap file encryption can significantly decrease performance. Only enableswap file encryption in situations where it is required.

l Enabled (1): The swap file is encrypted.l Disabled (0): The swap file is not encrypted.

LogFileCount


LogFileCount 50 No

DescriptionThe maximum number of log files to keep. After the maximum number of log files isreached, each time an additional file is created, the driver deletes the oldest log file.

LogFileSize


LogFileSize 20 No

DescriptionThe maximum size of each log file in megabytes (MB). After the maximum file size isreached, the driver creates a new file and continues logging.

www.simba.com 54


LogLevel


LogLevel 0 No

DescriptionUse this property to enable or disable logging in the driver and to specify the amount ofdetail included in log files.

Important:

Only enable logging long enough to capture an issue. Logging decreasesperformance and can consume a large quantity of disk space.

Set the property to one of the following values:

l 0: Disable all logging.l 1: Logs severe error events that lead the driver to abort.l 2: Logs error events that might allow the driver to continue running.l 3: Logs events that might result in an error if action is not taken.l 4: Logs general information that describes the progress of the driver.l 5: Logs detailed information that is useful for debugging the driver.l 6: Logs all driver activity.

When logging is enabled, the driver produces a log file namedSimbaODBCDriverforHubSpot.log in the location specified in the LogPathproperty.

LogPath


LogPath None Yes, if logging isenabled.

DescriptionThe full path to the folder where the driver saves log files when logging is enabled.

www.simba.com 55


Memory Manager Memory Limit


MemoryManagerMemoryLimit 1024 for the 32-bitdriver, or 2048 forthe 64-bit driver.

No

DescriptionThe maximum amount of RAM in megabytes (MB) that the driver can use to cache datafor SQL operations.

The data type of the value is String, but the value must be an integer.

Memory Manager Strategy


MemoryManagerStrategy 2 No

DescriptionThis option specifies the following driver behavior for executing SQL operations onnon-SQL data:

l How the driver restricts RAM usage for individual SQL operations.l How the driver responds when SQL operations require more RAM than theallotted amount.

l Whether to maximize the performance of fewer operations or to support moreconcurrent operations.

The total amount of RAM that can be used by all concurrent operations is alwaysdetermined by the memory limit (the MemoryManagerMemoryLimit setting).

Set the key to one of the following values:

l 1: Each operation is allotted an amount of RAM based on an internal calculation.If an operation requires more RAM than the allotted amount or if the memory limitis reached, then the driver stops the operation or operations and returns an out-of-memory error. This setting is recommended for situations where the drivershould not write to disk, such as in cloud deployments.

www.simba.com 56


l 2: Each operation is allotted an amount of RAM based on an internal calculation.If an operation requires more RAM than the allotted amount or if the memory limitis reached, then the driver creates swap files on disk and moves some of thecached data to those files in order to free up memory and continue the operationor operations. This setting is recommended if you need to run multiple concurrentqueries with good performance.

l 3: The first operation can consume as much RAM as necessary from theamounts specified by the memory limit and threshold, while subsequentoperations use the remaining amount. If the memory limit or threshold is reached,then the driver creates swap files on disk and moves some of the cached data tothose files in order to free up memory and continue the operation or operations.This setting is recommended if you need to maximize performance for a singlequery.

Memory Manager Swap Disk Limit


MemoryManagerSwapDiskLimit 0 No

DescriptionThe maximum total size of the swap files that the driver creates to temporarily cachedata on disk, in megabytes (MB).

When this option is set to 0, there is no limit to the size of the swap files.

Memory Manager Threshold Percent


MemoryManagerThresholdPercent 80 No

DescriptionThe maximum percentage of the memory limit (the MemoryManagerMemoryLimitsetting) that can be used by an existing SQL operation. The remaining memory limit isreserved for new operations.

The data type of the value is String, but the value must be an integer between 0 and100, inclusive.

www.simba.com 57


Proxy Host


ProxyHost None Yes, if connectingthrough an HTTP proxy.

DescriptionThe host name or IP address of an HTTP proxy that you want to connect through.

Proxy Password


ProxyPwd None Yes, if connecting toan HTTP proxy thatrequires authentication.

DescriptionThe password that you use to access the HTTP proxy.

Proxy Port


ProxyPort None Yes, if connectingthrough an HTTP proxy.

DescriptionThe number of the port that the HTTP proxy uses to listen for client connections.

www.simba.com 58


Proxy Uid


ProxyUid None Yes, if connecting toan HTTP proxy thatrequires authentication.

DescriptionThe user name that you use to access the HTTP proxy.

Swap File Path


SwapFilePath The default temporarydirectory for youroperating system.

No

DescriptionThe full path to the directory where the driver creates swap files to temporarily cachedata on disk.

TrustCertsPath


TrustCertsPath None Yes, if using the driver ona non-Windows machineand peer verification overSSL is enabled.

DescriptionThe full path of the .pem file containing trusted CA certificates for verifying the serverduring SSL authentication.

www.simba.com 59


Note:

This property is applicable only when using the driver on a non-Windowsmachine.

Use Encrypted Endpoints


UseEncryptedEndpoints Enabled (1) No

DescriptionThis option specifies whether the data source endpoints are encrypted using HTTPS.

l Enabled (1): The driver uses encrypted endpoints.l Disabled (0): The driver does not use encrypted endpoints.

Use Host Verification


UseHostVerification Enabled (1) onWindows, Disabled (0)on other platforms.

No

DescriptionThis option specifies whether the driver requires the host name in the server'scertificate to match the host name of the server when connecting over SSL.

l Enabled (1): The driver requires the host name in the server's certificate to matchthe host name of the server that you are connecting to.

l Disabled (0): The driver accepts all host names.

www.simba.com 60


Use Peer Verification


UsePeerVerification Enabled (1) onWindows, Disabled (0)on other platforms.

No

DescriptionThis option specifies whether the driver verifies the identity of the server whenconnecting over SSL.

l Enabled (1): The driver verifies the identity of the server.l Disabled (0): The driver does not verify the identity of the server.

If this option is enabled, you must provide a trusted certificate for verifying the server.For more information, see Configuring SSL Verification on Windows on page 14 orConfiguring SSL Verification on Non-Windows Machines on page 32.

Use Windows Proxy Settings


UseWindowsProxySettings Disabled (0) No

DescriptionThis option specifies whether the driver retrieves the proxy host and port through theInternet Options in Internet Explorer, when connecting through an HTTP proxy. Thisproperty is applicable only to Windows.

l Enabled (1): The driver retrieves the proxy host and port through InternetExplorer.

l Disabled (0): The driver does not retrieve the roxy host and port through InternetExplorer.

www.simba.com 61


Contact Us

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

Note:

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 the Magnitude Support Community athttp://magnitudesoftware.com/online-support/.

You can also follow us on Twitter @SimbaTech and @Mag_SW

www.simba.com 62

Installation and Configuration Guide Contact Us

http://magnitudesoftware.com/online-support/

Third-Party Trademarks

Microsoft, MSDN, Windows, Windows Server, Windows Vista, and the Windows startbutton are trademarks or registered trademarks of Microsoft Corporation or itssubsidiaries in Canada, United States and/or other countries.

HubSpot is a trademark or registered trademark of HubSpot, Inc. or its subsidiaries inCanada, the United States and/or other countries.

All other trademarks are trademarks of their respective owners.

www.simba.com 63

Installation and Configuration Guide Third-Party Trademarks

Third-Party Licenses

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

CityHash License

Copyright (c) 2011 Google, Inc.

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 ANDNONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHTHOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISINGFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OROTHER DEALINGS IN THE SOFTWARE.

CityHash, by Geoff Pike and Jyrki Alakuijala

http://code.google.com/p/cityhash/

cURL License

COPYRIGHT AND PERMISSION NOTICE

Copyright (c) 1996 - 2015, Daniel Stenberg, [email protected].

All rights reserved.

Permission to use, copy, modify, and distribute this software for any purpose with orwithout fee is hereby granted, provided that the above copyright notice and thispermission notice appear in all copies.

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 THE

www.simba.com 64

Installation and Configuration Guide Third-Party Licenses

http://code.google.com/p/cityhash/

mailto:[email protected]

AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGESOR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OROTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THESOFTWARE OR THE USE OR OTHER DEALINGS IN THE 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.

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 anysoftware 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



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.

www.simba.com 65


ICU License - ICU 1.8.1 and later

COPYRIGHT AND PERMISSION NOTICE

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


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 LIABLEFOR 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

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.

www.simba.com 66


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 GOODSOR 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 this

www.simba.com 67


http://www.openssl.org/

http://www.openssl.org/

distribution, 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

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. 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])"

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.

www.simba.com 68


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.]

POCO C++ Libraries License

Copyright © 2016, Applied Informatics Software Engineering GmbH.


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

The copyright notices in the Software and this entire statement, including the abovelicense grant, this restriction and the following disclaimer, must be included in allcopies 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-executableobject 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 WARRANTIESOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE ANDNON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS ORANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OROTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISINGFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OROTHER DEALINGS IN THE SOFTWARE.

pugixml License

This software is based on pugixml library (http://pugixml.org). pugixml is Copyright (C)2006-2015 Arseny Kapoulkine.

Copyright (c) 2006-2015 Arseny Kapoulkine



www.simba.com 69


http://www.appinf.com/

http://pugixml.org/

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

RapidJSON License

Tencent is pleased to support the open source community by making RapidJSONavailable.

Copyright (C) 2015 THL A29 Limited, a Tencent company, and Milo Yip. All rightsreserved.

If you have downloaded a copy of the RapidJSON binary from Tencent, please notethat the RapidJSON binary is licensed under the MIT License.

If you have downloaded a copy of the RapidJSON source code from Tencent, pleasenote that RapidJSON source code is licensed under the MIT License, except for thethird-party components listed below which are subject to different license terms. Yourintegration of RapidJSON into your own projects may require compliance with the MITLicense, as well as the other licenses applicable to the third-party componentsincluded within RapidJSON.

A copy of the MIT License is included in this file.

Other dependencies and licenses:

Open Source Software Licensed Under the BSD License:

The msinttypes r29Copyright (c) 2006-2013 Alexander ChemerisAll rights reserved.

Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:

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

l Redistributions in binary form must reproduce the above copyrightnotice, this list of conditions and the following disclaimer in thedocumentation and/or other materials provided with the distribution.

www.simba.com 70


l Neither the name of copyright holder nor the names of its contributorsmay be used to endorse or promote products derived from this softwarewithout specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS ANDCONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THEREGENTS AND CONTRIBUTORS BE LIABLE FOR ANY DIRECT,INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OFSUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, ORPROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ONANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, 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.

Open Source Software Licensed Under the JSON License:

json.orgCopyright (c) 2002 JSON.orgAll Rights Reserved.

JSON_checkerCopyright (c) 2002 JSON.orgAll Rights Reserved.

Terms of the JSON License:

Permission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "Software"), to deal inthe Software without restriction, including without limitation the rights to use,copy, modify, merge, publish, distribute, sublicense, and/or sell copies of theSoftware, 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 allcopies or substantial portions of the Software.

The Software shall be used for Good, not Evil.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANYKIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THEWARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR

www.simba.com 71


PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OFCONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR INCONNECTION WITH THE SOFTWARE OR THE USE OR OTHERDEALINGS IN THE SOFTWARE.

Terms of the MIT License:

Permission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "Software"), to deal inthe Software without restriction, including without limitation the rights to use,copy, modify, merge, publish, distribute, sublicense, and/or sell copies of theSoftware, 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 allcopies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANYKIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THEWARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OFCONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR INCONNECTION WITH THE SOFTWARE OR THE USE OR OTHERDEALINGS IN THE SOFTWARE.

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.

www.simba.com 72


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)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

zlib License

Copyright (C) 1995-2013 Jean-loup Gailly and Mark Adler

This software is provided 'as-is', without any express or implied warranty. In no eventwill the authors be held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, includingcommercial applications, and to alter it and redistribute it freely, subject to the followingrestrictions:1. The origin of this software must not be misrepresented; you must not claim that

you wrote the original software. If you use this software in a product, anacknowledgment in the product documentation would be appreciated but is notrequired.

2. Altered source versions must be plainly marked as such, and must not bemisrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution.

Jean-loup Gailly Mark Adler

[email protected] [email protected]

www.simba.com 73


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



SimbaHubSpotODBCDriverwith SQLConnector...

Documents

Transcript of SimbaHubSpotODBCDriverwith SQLConnector...