Quick Start: Progress DataDirect® for ODBC for

Apache Spark SQLTM Wire Protocol Driver on

Windows (32-bit and 64-bit)

The following basic information enables you to connect with and test your driver immediately after installation. For installation instructions, see the Progress DataDirect for ODBC Drivers Installation Guide. This Quick Start covers the following topics:

Connecting to a Database

Testing the Connection

Tuning the Driver for Optimal Performance

Connecting to a Database

1       Start the ODBC Administrator to display a list of user data sources.

2       On the User DSN tab, click Add to display a list of installed drivers. Select the appropriate driver from the list and click Finish to display the driver Setup dialog box.

3       On the General tab, provide the required information; then, click Apply. The General tab has the following required options:

       Host Name: Type the URL or IP address of the interface to which you want to connect.

       Port Number: Type the port number of the server listener. The default is 10000.

       Database Name: Type the name of the database to which you want to connect.

4.      For Microsoft Access and Tableau users, click on the Advanced tab. Provide the following required value for the Max String Size option; then, click Apply.

       Max String Size: The maximum size of columns of the String data type that the driver describes through result set descriptions and catalog functions.

  For Microsoft Access: Type 255.

  For Tableau: Type a value from 255 to 4000 that suits your environment.

Testing the Connection

1       At the bottom of the Driver Setup dialog box, click Test Connect to attempt to connect to the data source using the connection properties that you specified. A logon dialog box appears. Note that the information you enter in the logon dialog box during a test connect is not saved. Click OK.

If the driver can connect, it releases the connection and displays a connection established message. If the driver cannot connect because of an improper environment or incorrect connection value, it displays an appropriate error message. Click OK.

2       Click OK or Cancel at the bottom of the Driver Setup dialog box. If you click OK, the values you have specified become the defaults when you connect to the data source.

Tuning the Driver for Optimal Performance

The driver has connection options that directly affect performance. To tune the driver for optimal performance, set the following options:

If you know the typical fetch size for your application

Set Array Size on the Advanced tab to suit your environment. This option specifies the number of cells the driver retrieves. By increasing the value of Array Size, you increase the number of rows the driver will retrieve from the server for a fetch. Smaller values can improve the initial response time of the query. Larger values improve overall fetch times at the cost of additional memory and slower response time.

Note: If the fetch size exceeds the available buffer memory of the server, an out of memory is returned when attempting to execute the fetch. If you receive this error, decrease the value specified until fetches are successfully executed.

If you know the size of images, pictures, long text, or long binary data

Adjust Default Buffer Size for Long/LOB Columns on the Advanced tab. To improve performance, a buffer size can be set to accommodate the maximum size of the data. The buffer size should only be large enough to accommodate the maximum amount of data retrieved; otherwise, performance will be reduced.

If your application needs to access a database objects owned only by the current user

Enable Use Current Schema for Catalog Functions on the Advanced tab to improve performance. When this option is enabled, the driver returns only database objects owned by the current user when executing catalog functions. Calls to catalog functions are optimized by grouping queries.

If your application requires encryption of data

Controlled by Encryption Method on the Security Tab. Data encryption may adversely affect performance because of the additional overhead (mainly CPU usage) required to encrypt and decrypt data.

© 2016. Progress Software Corporation. All rights reserved.

2/16, 8.0.2