Configure External systems

Data Studio includes drivers that allow you connect to a wide range of external systems.

A wide range of JDBC drivers are included in the Data Studio deployment.

You can also download and deploy your own JDBC (Java Database Connectivity) driver, which must be a type 4 driver and be supported by Java 8. Once a custom driver is deployed, you will be able to create and manage External system connections just as you do with the native drivers. To deploy a custom driver:

1. Download the JDBC driver you want to use. This will typically be a single file with a .jar extension.
2. Stop the Data Studio Database service.
3. Copy the driver to the \drivers\jdbc folder in the database root directory. By default this will be C:\ApertureDataStudio\drivers\jdbc. If a driver is comprised of multiple jar files then the auxiliary jars should be placed in the lib subdirectory.
4. Restart the Data Studio Database service.
5. Log in to Data Studio as a user that has the "Manage Connections to External Systems" capability, and configure a connection using the new driver in System > External systems > Add new external system.
6. With the type JDBC selected, the DBMS dropdown should now display the new custom driver, with the word "Custom" prefixing the driver name and version.
   • If the driver isn't configured in either datadirectJdbc.json or customJdbc.json then it will appear in the UI with the name "CUSTOM_N (source jar file name) version" where N is an index of each unknown driver (e.g. "CUSTOM_1 (csvjdbc-1.0-36.jar) 1.0").
   • If the driver is already configured in customJdbc.json then it will appear in the UI with the name "Custom DBMsname version" (e.g. "Custom Snowflake 3.11").
7. Follow the driver's documentation to configure the connection.

Connection parameters

1. Hostname: Host name of the computer where Oracle Database is installed.
2. Port: The JDBC port number that the DBMS server uses to listen for connection requests.
3. SID: The System Id (optional).

The connection string template is: jdbc:experian:oracle://hostname:port;SID=SID;LoginTimeout=15;UseServerSideUpdatableCursors=true. Additional connection properties are detailed in the DataDirect Oracle JDBC driver documentation.

Authentication parameters

1. Username: Oracle Database username
2. Password

Using Service Name instead of SID

To connect to an Oracle server using a Service Name rather than SID, leave the SID field blank and specify the Oracle service name as a user connection property, ServiceName=my.server.com. This property is mutually exclusive with the SID property.

Use the service name to specify connections to an Oracle Real Application Cluster (RAC) because the nodes in a RAC system share a common service name. Service name is also typically used to connect to Pluggable databases (PDBs).

Troubleshooting

The specified SID (or service name) was not recognized by the Oracle server

Error messages:

• ORA-12505 Connection refused, the specified SID () was not recognized by the Oracle server
• ORA-12514 Connection refused, the specified service Name () was not recognized by the Oracle server

This error can occur if the Oracle database server is configured as RAC (multiple servers, with a load balancer). You may need to use the LoadBalancing=true and AlternateServers=(server2:server2port) user connection properties in the connection configuration.

Invalid identifier

Error:

• ORA-00904: Invalid identifier

This error can occur when attempting to preview or load data into Data Studio, if the schema has not been defined in the External system connection and the table exists in more than one schema. To resolve, specify the schema in the connection's advanced settings, to avoid using the Oracle user's default schema.

Transliteration failed, reason: invalid UTF8 data

When attempting to load data from a table, no records are shown and the logs contain "Transliteration failed, reason: invalid UTF8 data". This issue occurs while processing the table, which contains data in a codepage other than UTF-8.

To resolve, set the CodePageOverride connection property, or alternatively use the Oracle thin driver as an alternative custom JDBC driver.

Connection parameters

The following fields are required for connection:

1. Hostname: Hostname of the computer where the SQL server Database is installed. An instance name or port number may also be specified.
2. Database: Database name.
3. Schema: Schema name.

The connection string template is: jdbc:experian:sqlserver://;allowPortWithNamedInstance=true;DatabaseName=;LoginTimeout=15;UseServerSideUpdatableCursors=true;SelectMethod=cursor

Additional connection properties are detailed in the DataDirect SQLServer JDBC driver documentation.

Specify port or named instance

The hostname field can be used to define a port and instance name.

• If using default port (1433) or instance (MSSQLSERVER), just enter the hostname.
• To specify a port, enter the port number in the format "hostname:port".
• To specify a named instance, enter the instance name in the format "hostname\instance".

When specifying the location of the SQL server instance, you should never provide both an instance name and port number together.

Azure SQL Server

If you're connecting to Microsoft Azure SQL two additional connection properties need to be added. This is because Microsoft Azure SQL requires communication using SSL.

1. EncryptionMethod=SSL
2. ValidateServerCertificate=false. If set to true, the certificate needs to be available in the database server trust store. The certificate must be issued by a trusted Certificate Authority. If set to false, there will be no validation on the certificate.

Authentication parameters

The SQL Server driver supports several different authentication methods for establishing a connection. The default method is SQL Server authentication with a username and password.

To connect using Windows Authentication (NTLMv2), use the connection property AuthenticationMethod=ntlm2java. When adding credentials, enter the Windows credentials that will be used to connect to the Microsoft SQL server instance.

To use Azure Active Directory (Azure AD) authentication, set AuthenticationMethod=ActiveDirectoryPassword. In addition, a value must be specified for the HostNameInCertificate property, and the connection must be configured to use SSL.

Troubleshooting

Cannot open database <"Database name">

If you receive this error when attempting to make a connection, the login failed. This usually occurs either because the database name is incorrect or connection credentials do not have the required permissions.

Ensure that you have the right database name entered and check and ensure valid permissions for the credentials.

View Column Map Failure

The error displays when exporting data from Data Studio to SQL Server. It usually occurs when an export step in a workflow is attempting to INSERT or UPDATE data into a table where the data doesn't match the target schema.

Ensure that the data that you're exporting from Data Studio matches the data types of the target table's schema. You can use the Conversion functions in Data Studio to convert the values in your columns to the intended data type.

Column cannot be modified because it is either a computed column or is the result of a UNION operator

The error displays when exporting data from Data Studio to SQL Server. This error can occur when you're trying to export (INSERT) into a SQL table where one of the columns is a computed column.

The solution is to use a Map to target step before the export and leave any computed columns unmapped.

Invalid object name

Error when loading data from SQL server into Data Studio. The credentials used may not have the necessary permission to preview and load the data for the specified schema.

Ensure that the credentials used have the required permissions to preview and load data (using SELECT) from the relevant table or view in the specified schema. If you're connecting with a user whos default schema is different to the specified schema, check the Force JDBC schema name setting in the external system's configuration.

A user name must be specified when using pure Java NTLM

This authentication error can happen when using the same Windows credentials to connect using two different external systems to different domains on the same SQL Server instance. If the error appears when testing the connection, check that you're using nltm2java as the AuthenticationMethod connection property, and not nltmjava.

Type datetimeoffset loaded as Alphanumeric in Data Studio

By default, the driver loads datetimeoffset values (datetime with timezone offset) as type VARCHAR, which will be alphanumeric data type in Data Studio. To interpret these values as TIMESTAMP and load as dates instead, set the user connection property FetchTSWTZAsTimestamp=true.

Timestamps are converted to UTC on load into Data Studio.

The Microsoft Dynamics 365 driver supports two different methods of authentication. NTLM is typically used when Dynamics is hosted on premise, and requires a username and password to authenticate. OAuth is typically used when Dynamics is hosted in the cloud and requires more configuration.

Connection parameters (NTLM)

1. Service URL - The url that handles service requests for the database. It should be in the format: https://myonpreminstance.sso3.dynamics365.net/api/data/v9.1/

Authentication parameters (NTLM)

1. User name - the user name for connecting to the service.
2. Password - the above user's password.

Connection parameters (OAuth)

These settings can be obtained from the dynamics server:

1. Service URL - The url that handles service requests for the database. It should be in the format: https://sandbox.api.ds.dynamics.com/api/data/v9.1/.
2. Authentication URI - The Microsoft endpoint that handles authentication. It should be in the format: https://login.microsoftonline.com/1234567-12345-1234-1234-123456789abc/oauth2/v2.0/authorize.
3. Token URI - the Microsoft endpoint that handles granting of new authentication tokens. It should be in the format: https://login.microsoftonline.com/1234567-12345-1234-1234-123456789abc/oauth2/v2.0/token.
4. Scope URI - the Dynamics endpoint that handles the permissions when authenticating. It should be in the format: https://sandbox.api.ds.dynamics.com/user_impersonation offline_access.

Authentication parameters (OAuth)

1. Client ID - The client id for your application.
2. Client Secret - The client secret for your application.
3. Access Token - the value of the access token obtained from external sources.
4. Refresh Token - the value of the refresh token obtained from external sources.

Troubleshooting

1. The MS Dynamics 365 driver can take minutes to test. If you find that your Test button is timing out, set the JDBC timeout setting in Aperture Data Studio under Settings->Loading to 360 seconds and try again.
2. The refresh token is not always necessary - if not entering any value is sufficient.
3. The Access token and Refresh token will need to be generated externally. The access token can timeout quickly, so check that your token is still valid if you can no longer connect to a database.
4. For further documentation on this driver see the DataDirect for JDBC for Microsoft Dynamics 365 Driver documentation.

Connection parameters

1. Hostname: This specifies the base Salesforce URL to use for logging in, for example um5.salesforce.com or experian.my.salesforce.com. It will be the same base URL used for browsing to the Salesforce classic web application. This driver does not support the Lightning URL. For example, um5.lightning.force.com is not a valid hostname for the driver. If you're unsure, you can use the default Hostname login.salesforce.com.
2. Schema: Optional, default SFORCE.

The template connection string is: jdbc:experian:sforce://;LoginTimeout=30;StmtCallLimit=0.

Additional connection properties are detailed in the DataDirect Salesforce JDBC driver documentation.

Authentication parameters

1. Username: Specify the username that is used to connect to the Salesforce instance.
2. Password: Specify the password to use to connect to your Salesforce instance. Typically, the username and password will be the same as the details you use to log into the Salesforce web UI.
3. Security Token: Specifies the security token required to make a connection to a Salesforce instance that is configured for a security token. The security token is not required when Salesforce has been configured for Trusted IP Ranges and the user is logging in from a trusted IP address.

Troubleshooting

Salesforce schema has changed. Columns or tables not shown

If your Salesforce schema has changed (e.g. columns/tables have been added or removed), the driver will need to recreate the local schema mapping.

If the schema change is a one-off event, set the SchemaMap property to force the driver to create a new schema map the next time a connection is established, while retaining the old mapping for reference.

If the schema is likely to change regularly, you can configure the driver to always refresh the schema map when establishing a connection. To do this, set the following: CreateMap=forceNew. If you get an error "The specified configuration options do not match the options used to initially create the schema map", you'll have to force the driver to create a new schema map using the SchemaMap property. If you've already defined this, change it to a new value to force the creation of new schema map.

Reset your security token

To reset your security token via the Salesforce UI, browse to your personal settings and click on Reset My Security Token. An email will be sent with your new token. Some organizations will only allow administrators to reset users' tokens.

Error reading XMLStreamReader

You may be using the Salesforce lightning app hostname. Change the hostname URL to Salesforce Classic. For example, use ap160.salesforce.com instead of ap160.lightning.force.com.

The configuration options used to open the database do not match the options used to create the database

You may see this when making changes to a connection that require the mapping schema to be updated.

Use the SchemaMap connection property. The value for this property is either a name or the absolute path and name (including the .config extension) of the local schema mapping file.

Error when loading data from the Salesforce instance into Data Studio - Timeout on load (or preview) from Salesforce

There is likely to have been a timeout while the driver waits for a response to the web service request. Add the connection property WSTimeout and/or WSRetryCount.

Control which columns are visible, and column name formatting

The custom connection property ConfigOptions controls how Salesforce table columns are mapped in the driver:

1. The driver exposes Salesforce audit fields (e.g. ISDELETED) and the master record ID (MASTERECORDID) field. To hide AuditColumns set ConfigOptions to (AuditColumns=none).
2. The driver exposes the names of system fields as they exist in the Salesforce data model, unchanged. To have the prefix Sys_ for system columns, set ConfigOptions to (MapSystemColumnNames=1).
3. The driver adds the __c suffix to custom table and column names when mapping the Salesforce data model. To remove the _C suffix for custom tables and column names set ConfigOptions to (CustomSuffix=strip).
4. To change the casing of the column names so that they're not all uppercase, set ConfigOptions to (UppercaseIdentifiers=false).
5. These settings can be combined by setting 'ConfigOptions' to (AuditColumns=none;MapSystemColumnNames=1;CustomSuffix=strip; UppercaseIdentifiers=false).

Connection parameters

1. Hostname: Host name of the computer where the Hive Database is installed.
2. Port: The Hive connection port number (default 9999).

The template connection string is: jdbc:experian:hive://:9999;LoginTimeout=15. Additional connection properties are detailed in the DataDirect Hive JDBC driver documentation.

Authentication parameters

1. Username: Specify the username that is used to connect to the Hive instance.
2. Password: Specify the password to use to connect to your Hive instance.

Connecting to Azure HDInsight

To connect to HDInsight, Hostname will be set to the cluster URL, for example mycluster.azurehdinsight.net, and you will need to specify the following connection properties:

1. databaseName, set to the name of the internal or external database in your cluster that you want to connect to. If not specified, this defaults to default.
2. TransportMode=http.
3. EncryptionMethod=SSL.
4. HTTPPath set to the path of HTTPS endpoint, for example /hive2.

When establishing the connection, use the HDInsight cluster admin name and password to authenticate.

Troubleshooting

Thrift errors when attempting to Insert or Update

To avoid Thrift errors when attempting to Insert or Update rows in a Hive table, try increasing the value for the connection property ArrayInsertSize.

Connection parameters

1. Project: The project name associated with your Google BigQuery account.
2. Dataset: The Dataset name.

The template connection string is: jdbc:experian:googlebigquery:Project=;Dataset=. Additional connection properties are detailed in the DataDirect BigQuery JDBC driver documentation.

The driver supports OAuth 2.0 and service account authentication.

Authentication using OAuth 2.0

To use OAuth 2.0, you will add user connection properties to enter the access and refresh tokens.

1. Set the AuthenticationMethod = oauth2.
2. Set at least one of the following properties:
   • AccessToken: Set this to specify the access token you have obtained to authenticate to Google BigQuery.
   • RefreshToken: Set this to specify the refresh token you have obtained to authenticate to Google BigQuery.

     If a value for the AccessToken property is not specified, the driver uses the value of the RefreshToken property to make a connection. If both values are not specified, the driver cannot make a successful connection. If both are specified, the driver uses the AccessToken value; however, if the AccessToken value expires, it uses the RefreshToken value to generate a new AccessToken value.

3. Set the ClientID property to specify the consumer key for your application.
4. Set the ClientSecret property to specify the consumer secret for your application.
5. Optionally, set the Scope property to specify the OAuth scope. It limits the permissions granted by an access token.

Authentication with a service account

A service account is a type of Google account that represents an application instead of an individual end user. For a successful service account authentication, you need:

1. Private key file or Private key:
   • The private key file is a .json or .p12 file that contains the key required to authenticate API calls. You can download it from the Google Cloud Platform (GCP) Console.
   • The private key is contained in the private key file downloaded from the GCP Console.
2. Service account email address: A unique email address that is provisioned while creating a service account.

To configure the driver to use service account authentication, set the following connection properties:

1. Set AuthenticationMethod=serviceaccount.
2. Set the ServiceAccountEmail property to specify your service account's email address.
3. Set either the ServiceAccountKeyContent property or the ServiceAccountPrivateKey property:
   • ServiceAccountKeyContent specifies the private key required to authenticate to Google BigQuery. Use this property if you do not want to persist the private key file in your environment.
   • ServiceAccountPrivateKey specifies the full path to the .json or .p12 file that contains the private key. The driver extracts the private key value from the specified file and uses it to authenticate the user to the database. Use this property if it is preferable to persist the private key file.

Troubleshooting

List of tables shows incorrectly, or "table… was not found" on load

This error is typically caused by an out-of-date map of the data model. To force the schema to refresh, add the property RefreshSchema=true or alternatively use CreateMap=session to store the map in memory.

Connection parameters

1. Hostname: The name of the computer on which the MySQL database server is running.
2. Port: The MySQL server connection port (default is 3306).
3. Database The Database name.

The template connection string is: jdbc:experian:mysql://:3306;DatabaseName=;LoginTimeout=15

Additional connection properties are detailed in the DataDirect MySQL JDBC driver documentation.

Authentication parameters

1. Username
2. Password

Troubleshooting

Connections to MySQL Community Server are not supported

The Progress DataDirect MySQL JDBC driver shipped with Data Studio does not support MySQL Community Server versions (including Amazon Aurora MySQL). To connect to a database based on MySQL Community versions, download the MySQL Connector/J driver and deploy the mysql-connector-java-.jar file as a new custom driver.

Connection parameters

1. Hostname - The name of the computer on which the PostgreSQL database server is running
2. Port - The PostgreSQL server connection port (default is 5432)
3. Database- The Database name

The template connection string is: jdbc:experian:postgresql://:5432;DatabaseName=;LoginTimeout=15. Additional connection properties are detailed in the DataDirect PostgreSQL JDBC driver documentation.

Authentication parameters

1. Username
2. Password

Connection parameters

1. Hostname - The name of the computer on which the Redshift database server is running
2. Port - The Redshift server connection port (default is 5439)
3. Database- The Database name

The template connection string is: jdbc:experian:redshift://:5439;DatabaseName=;LoginTimeout=15. Additional connection properties are detailed in the DataDirect Redshift JDBC driver documentation.

Authentication parameters

1. Username
2. Password

Connection parameters

1. Company - The name of the computer on which the Jira database server is running
2. Schema - The schema name

The template connection string is: jdbc:experian:jira:;User=;Password=
Additional connection properties are detailed in the DataDirect Jira JDBC driver documentation.

Authentication parameters

1. Username
2. Password

The Autonomous REST Connector is a JDBC driver that allow Data Studio to codelessly connect to any RESTful API data source to load data.

You can connect to the REST service either directly via and endpoint, or by using a path to a .rest file. If you're using the endpoint directly, default mappings are generated to map JSON structures to relational tables. Alternatively, a .rest file can be created to define endpoints, mappings, and paging.

Connection parameters

One of the following settings must be provided:

1. REST configuration file: Specifies the name and location of the input REST file that contains a list of endpoints to sample, PUSH request definitions, and configuration information.
2. REST endpoint: Specifies the endpoint to sample when not using an input REST file.
3. AuthenticationMethod: Determines which authentication method the driver uses during the course of a session. Options include None, Basic, HttpHeader, OAuth2, UrlParameter and Custom.

The template connection string is: jdbc:experian:autorest:Config=;Sample=. For additional connection properties and more information on creating a REST file and the authentication options, see the DataDirect Autonomous REST JDBC driver documentation.

Authentication parameters

The username and password fields can be left blank if alternative authentication methods are used and authentication parameters are provided in the connection params.

1. Username: Specifies the user name that is used to connect to the service.
2. Password: A password that is used to connect to the service.

Connection parameters

1. Hostname: Host name of the computer where the Cassandra Database is installed.
2. Port: The Cassandra connection port number (default 9042).
3. Keyspace: The keyspace name.

The template connection string is: jdbc:experian:cassandra://:9042;KeyspaceName=;LoginTimeout=15. Additional connection properties are detailed in the DataDirect Cassandra JDBC driver documentation.

Authentication parameters

1. Username: Specify the username that is used to connect to the Cassandra database.
2. Password: Specify the password to use to connect to your Cassandra database.

Connection parameters

1. Hostname: Host name of the computer where the DB2 Database is installed.
2. Port: The DB2 connection port number (default 50000).
3. Database: The database name.

The template connection string is: jdbc:experian:db2://:50000;DatabaseName=;LoginTimeout=15. Additional connection properties are detailed in the DataDirect DB2 JDBC driver documentation.

Authentication parameters

1. Username: Specify the username that is used to connect to the DB2 database.
2. Password: Specify the password to use to connect to your DB2 database.

Connection parameters

1. Hostname: Host name of the computer where the Greenplum Database is installed.
2. Port: The Greenplum connection port number (default 5432).
3. Database: The database name.

The template connection string is: jdbc:experian:greenplum://:5432;DatabaseName=;LoginTimeout=15. Additional connection properties are detailed in the DataDirect Greenplum JDBC driver documentation.

Authentication parameters

1. Username: Specify the username that is used to connect to the Greenplum database.
2. Password: Specify the password to use to connect to your Greenplum database.

Connection parameters

1. Hostname: Host name of the computer where the Informix Database is installed.
2. Port: The Informix connection port number (default 1526).
3. Server: The name of the Informix server.
4. Database: The database name.

The template connection string is: jdbc:experian:informix://:1526;InformixServer=;DatabaseName=;LoginTimeout=15. Additional connection properties are detailed in the DataDirect Informix JDBC driver documentation.

Authentication parameters

1. Username: Specify the username that is used to connect to the Informix database.
2. Password: Specify the password to use to connect to your Informix database.

Connection parameters

1. Hostname: Host name of the computer where the MongoDB Database is installed.
2. Port: The MongoDB connection port number (default 27017).
3. Schema Definition: Specifies the fully qualified path of the configuration file where the relational map of native data is written. The driver looks for this file when connecting to a MongoDB server. If the file does not exist, the driver creates one.
4. Database: The database name.

The template connection string is: jdbc:experian:mongodb://:27017;SchemaDefinition=;DatabaseName=;LoginTimeout=15. Additional connection properties are detailed in the DataDirect MongoDB JDBC driver documentation.

Authentication parameters

1. Username: Specify the username that is used to connect to the MongoDB database.
2. Password: Specify the password to use to connect to your MongoDB database.

Connection parameters

1. Company: The company identifier issued by Oracle Eloqua during the registration process.
2. Username
3. Password

The template connection string is: jdbc:experian:eloqua:Company=;User=;Password=. Additional connection properties are detailed in the DataDirect Eloqua JDBC driver documentation.

Authentication parameters

1. Username: Specify the username that is used to connect to the Eloqua database.
2. Password: Specify the password to use to connect to your Eloqua database.

Connection parameters

1. Login Host: the base URL of the Oracle Sales Cloud site.

The template connection string is: jdbc:experian:oraclesalescloud//. Additional connection properties are detailed in the DataDirect Sales Cloud JDBC driver documentation.

Authentication parameters

1. Username: Specify the username that is used to connect to the Sales Cloud database.
2. Password: Specify the password to use to connect to your Sales Cloud database.

Connection parameters

1. Login Host: The base URL of the Oracle Service Cloud site.
2. Interface name: deprecated.

The template connection string is: jdbc:experian:oracleservicecloud:LoginHost=;InterfaceName=;user=;password=;LoginTimeout=15. Additional connection properties are detailed in the DataDirect Service Cloud JDBC driver documentation.

Authentication parameters

1. Username: Specify the username that is used to connect to the Service Cloud database.
2. Password: Specify the password to use to connect to your Service Cloud database.

Connection parameters

1. Hostname: Host name of the computer where the OpenEdge Database is installed.
2. Port: The OpenEdge connection port number (default 2003).
3. Database: The database name.

The template connection string is: jdbc:experian:openedge://:2003;DatabaseName=;LoginTimeout=15. Additional connection properties are detailed in the DataDirect OpenEdge JDBC driver documentation.

Authentication parameters

1. Username: Specify the username that is used to connect to the OpenEdge database.
2. Password: Specify the password to use to connect to your OpenEdge database.

The Snowflake driver supports UserID/Password authentication.

Connection parameters

1. Account name: Specifies the full name of your account and the region where it is hosted. The full account name may include additional segments that denote region and cloud platform.
2. Database name: Specifies the name of the database to which you are connecting.
3. Partner Application Name: Snowflake partner use only. Specifies the name of a partner application to which you are trying to connect. This property is useful for users who have an existing partner contract with Snowflake and are using the driver with a Snowflake partner application or plug-in.
4. Schema: Specifies the default schema to use for the specified database once connected. The specified schema should be an existing schema for which the specified default role has privileges.
5. Warehouse: Specifies the virtual warehouse to use once connected. The specified warehouse should be an existing warehouse for which the specified default role has privileges.

The template connection string is: jdbc:experian:snowflake:accountname=;databasename=;partnerapplicationname=;schema=;warehouse=;. Additional connection properties are detailed in the DataDirect Snowflake JDBC driver documentation.

Authentication parameters

1. Username: Specifies the user name that is used to connect to Snowflake.
2. Password: A password that is used to connect to the service.

Connection parameters

1. Hostname: Host name of the computer where the Spark SQL Database is installed.
2. Port: The Spark SQL connection port number (default 9999).
3. Database: The database name.

The template connection string is: jdbc:experian:sparksql://:9999;DatabaseName=;LoginTimeout=15. Additional connection properties are detailed in the DataDirect Spark SQL JDBC driver documentation.

Authentication parameters

1. Username: Specify the username that is used to connect to the Spark SQL database.
2. Password: Specify the password to use to connect to your Spark SQL database.

Connection parameters

1. Hostname: Host name of the computer where the Sybase Database is installed.
2. Port: The Sybase connection port number (default 5000).
3. Database: The database name.

The template connection string is: jdbc:experian:sybase://:5000;DatabaseName=;LoginTimeout=15. Additional connection properties are detailed in the DataDirect Sybase JDBC driver documentation.

Authentication parameters

1. Username: Specify the username that is used to connect to the Sybase database.
2. Password: Specify the password to use to connect to your Sybase database.

• SELECT * FROM customers WHERE age > 50
• SELECT * FROM customers LIMIT 100
• SELECT name FROM customers ORDER BY age
• SELECT * FROM customers INNER JOIN employees ON customers.person_id = employees.person_id