Salesforce Marketing Cloud

Building the JDBC URL

After installing the license, open the connection management page by running java -jar kingswaysoft.jdbc.jar. Enter the required details to generate the JDBC connection URL. Click Test Connection to test the generated URL, or Copy to Clipboard to copy the connection string for use in your application.

Note: If the license is not installed, you can still use the connection manager to generate a JDBC URL; however, the Test Connection feature will be disabled.

General Page

The General page allows you to specify connection properties and login credentials for the Salesforce Marketing Cloud REST service.

connectionmanage

General Settings

Subdomain: The Subdomain is the unique identifier that identifies your specific Marketing Cloud tenant.
Account Id: The Account Id is the unique identifier for a specific Business Unit within your Marketing Cloud account.
API Throttling Rate: The API Throttling Rate will limit the number of requests that can be sent per second. Set this value to 0 to disable API throttling.

Authentication Methods for Salesforce Marketing Cloud

Server-to-Server

Use your Client ID and Client Secret to authenticate with the Marketing Cloud API.

Client ID: The Client ID option allows you to specify the unique ID which identifies the application making the request.
Client Secret: The Client Secret option allows you to specify the client secret belonging to your app.
Scope: Optional. Set the scopes to request when requesting a token. Ensure that the selected scopes are available for your app.

Authorization Code

A saved token file and token password can be used to establish a connection. If you wish to generate a new token file, click Generate Token File to go through the token generation process, save the token file locally, and use the specified token password to connect.

Generate Token File
Path To Token File: The path to the token file on the file system.
Token File Password: The Password for the token file.

Test Connection

After completing the configuration for all required connection and authentication settings in the JDBC Connection Manager, you can use the Test Connection button to validate your configuration and verify API requests will authenticate successfully.

Advanced Settings Page

The Advanced Settings page allows you to specify advanced settings for the connection.

connectionmanage

Proxy Server Settings

Proxy Server Settings

Proxy Mode

The Proxy Mode option allows you to specify how you want to configure the proxy server setting. There are three options available.

No Proxy
Auto-detect (Use system configured proxy)
Manual

Proxy Server

Using the Proxy Server option allows you to specify the name of the proxy server for the connection.

Port

The Port option allows you to specify the port number of the proxy server for the connection.

Username (Proxy Server Authentication)

The Username option (under Proxy Server Authentication) allows you to specify the proxy user account.

Password (Proxy Server Authentication)

The Password option (under Proxy Server Authentication) allows you to specify the proxy user's password.

Miscellaneous Settings

Miscellaneous Settings

Timeout (secs)

The Timeout (secs) option allows you to specify a timeout value in seconds for the connection. The default value is 120 seconds. Specify 0 for an infinite timeout.

Retry on Intermittent Errors

The retry on intermittent errors determines if requests will be retried when there is an error. If this option is checked requests will be retried up to 3 times.

Ignore Certificate Errors

This option can be used to ignore those SSL certificate errors when connecting to the target server.

Warning: Enabling the "Ignore Certificate Errors" option is generally NOT recommended, particularly for production instances. Unless there is a strong reason to believe the connection is secure - such as the network communication is only happening in an internal infrastructure, this option should be unchecked for best security.

Note: When this option is enabled, it applies to all HTTP-based SSL connections in the same job process.

Concurrent Writing Threads

This option can be used to set the number of threads to be used during write operations. This can improve performance during large-volume write operations.

Bulk Polling Interval (secs)

This value controls how often (in seconds) the driver polls Salesforce Marketing Cloud to check the status of bulk operations.

Using the JDBC Driver

This section provides examples that use JDBC classes such as Connection, Statement, and ResultSet to manage interactions with Salesforce Marketing Cloud data. It covers regular statements and prepared statements for complex or frequently executed queries.

Custom Objects

The driver supports custom object discovery. Custom objects are prefixed with customobject_. Query system.tables to view these custom objects, as well as all other tables and what actions they support.

Executing Statements

After you have connected from your code, you can execute SQL statements using the Statement class. For connection details, see Connecting with DriverManager or Connecting with DataSource. For parameterized statements, see Executing Prepared Statements.

The driver supports passing some connection options directly within the query. Query level options will override connection level properties. Append the clause USING OPTIONS (\{option\}=\{value\}) to your INSERT/UPDATE/DELETE/UPSERT query. This clause is optional.

For example, to override the property BatchSizeForWriting for a specific query, set the clause to USING OPTIONS (batchsize=N), where N is the size of the batch to write. This can be useful when executing multiple statements with different batch sizes without having to re-initialize the connection.

SELECT

Use the Statement class's generic execute method or the executeQuery method to execute SQL statements that return data. To retrieve the results of a query, call the getResultSet method of the Statement.

String sql = "SELECT * FROM hub/campaigns WHERE id = 1";
try {
    ResultSet resultSet = statement.executeQuery(sql);
    LOGGER.info(resultSet.toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

INSERT

Use either the generic execute method or the executeUpdate method of the Statement class to execute an INSERT operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the inserted data's ID, exceptions raised during execution, and details of the affected data.

String sql = "INSERT INTO hub/campaigns (name, description) VALUES ('JdbcHubCampaign', 'Created by Jdbc')";

try {
    int result = statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
4561,null,null,{"name":"JdbcHubCampaign","description":"Created by Jdbc"},false

Custom objects may also support the INSERT operation. Query system.columns using the custom object table name to view columns of the custom object, as well as what actions each column supports.

String sql = "INSERT INTO customobject_PI_CONTENT (title, availability, uuid, content_id) VALUES "
           + "('Test', true, 'acde070d-8c4c-4f0d-9d8a-162843c10333', '1')";

try {
    int result = statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

UPDATE

Use either the generic execute method or the executeUpdate method of the Statement class to execute an UPDATE operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the updated data's ID, exceptions raised during execution, and details of the affected data.

String sql = "UPDATE hub/campaigns SET name = 'JdbcUpdateHubCampaign' WHERE id = 4561";
try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
4561,null,null,{"name":"JdbcUpdateHubCampaign"},false

DELETE

Use either the generic execute method or the executeUpdate method of the Statement class to execute a DELETE operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the deleted data's ID, exceptions raised during execution, and details of the affected data.

String sql = "DELETE FROM hub/campaigns WHERE id = 4561";
try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
null,null,null,null,false

UPSERT

Using the UPSERT operation, you can either insert or update an existing record in one call.

Not all tables support the upsert operation. Query the system.tables table to identify which tables support UPSERT operations.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the ID of upserted data, exceptions raised during execution, and the data affected by the upsert.

String sql = "UPSERT INTO hub/dataevents/rowset (dataExtensionId, keys, values) VALUES "
           + "('1a2b3c4d-1a2b-1a2b-1a2b-1a2b3c4d5e6f', '{\"MemberId\": \"38bed58c-9b97-4e95-90bf-8f39e8f539e1\"}', "
           + "'{\"FirstName\": \"John\",\"Surname\": \"Doe\",\"RewardsPoints\": 23456,\"RewardsTier\": 3,\"Area\": \"Enfield\"}')";
try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
null,null,null,{"keys":{"MemberId":"38bed58c-9b97-4e95-90bf-8f39e8f539e1"},"values":{"FirstName":"John","Surname":"Doe","RewardsPoints":23456,"RewardsTier":3,"Area":"Enfield"}},false

Custom objects may also support the UPSERT operation. Query system.columns using the custom object table name to view columns of the custom object, as well as what actions each column supports.

String sql = "UPSERT INTO customobject_PI_CONTENT (title, availability, uuid, content_id) VALUES "
           + "('Test', true, 'acde070d-8c4c-4f0d-9d8a-162843c10333', '1') "
		   + "ON DUPLICATE KEY UPDATE UPSERTFIELDS = uuid";

try {
    int result = statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

Executing Prepared Statements

Using a PreparedStatement can improve performance when you need to execute a SQL statement multiple times with different parameters. Unlike a Statement object, a PreparedStatement object is provided with a SQL statement when it is created, which can then be executed with different values each time. This special type of statement is derived from the more general Statement class.

Below are the steps outlining how to execute a prepared statement:

Creating and Executing a Prepared Statement

Create a PreparedStatement

Use the prepareStatement method of the Connection class to instantiate a PreparedStatement.

For connection details, see Connecting with DriverManager or Connecting with DataSource.

Set Parameters

Declare parameters by calling the corresponding setter method of the PreparedStatement.
NOTE: The parameter indices start at 1.

Execute the PreparedStatement

Use the generic execute or executeUpdate method of the PreparedStatement.

Retrieve Results

Call the getResultSet method of the PreparedStatement to obtain the query results, which are returned as a ResultSet.

Iterate Over the Result Set

Use the next method of the ResultSet to iterate through the results. To obtain column information, use the ResultSetMetaData class. Instantiate a ResultSetMetaData object by calling the getMetaData method of the ResultSet.

SELECT

Use the PreparedStatement class's generic execute method or the executeQuery method to execute SQL statements that return data.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the retrieved data.

String sql = "SELECT * FROM hub/campaigns WHERE id = ?";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setInt(1, 1);
    boolean ret = ps.execute();
    if (ret) {
        ResultSet rs = ps.getResultSet();
        LOGGER.info(rs.toString());
    }
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

INSERT

Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute an INSERT operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the ID of inserted data, exceptions raised during execution, and the data affected by the insertion.

String sql = "INSERT INTO hub/campaigns (name, description) VALUES (?, ?)";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "JdbcHubCampaign");
    ps.setString(2, "Created by Jdbc");
    ps.executeUpdate();

    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
4561,null,null,{"name":"JdbcHubCampaign","description":"Created by Jdbc"},false

Custom objects may also support the INSERT operation. Query system.columns using the custom object table name to view columns of the custom object, as well as what actions each column supports.

String sql = "INSERT INTO customobject_PI_CONTENT (title, availability, uuid, content_id) VALUES "
           + "(?, ?, ?, ?)";

try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "Test");
    ps.setBoolean(2, true);
    ps.setString(3, "acde070d-8c4c-4f0d-9d8a-162843c10333");
    ps.setString(4, "1");
    ps.executeUpdate();

    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

UPDATE

Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute an UPDATE operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the ID of updated data, exceptions raised during execution, and the data affected by the update.

String sql = "UPDATE hub/campaigns SET name = ? WHERE id = ?";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "JdbcUpdateHubCampaign");
    ps.setInt(2, 4561);
    ps.executeUpdate();

    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
4561,null,null,{"name":"JdbcUpdateHubCampaign"},false

DELETE

Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute a DELETE operation.

String sql = "DELETE FROM hub/campaigns WHERE id = ?";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setInt(1, 4561);
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    e.printStackTrace();
}

id,errorcode,errormessage,processdata,haserrors
null,null,null,null,false

UPSERT

Using the UPSERT operation, you can either insert or update an existing record in one call.

Not all tables support the upsert operation. Query the system.tables table to identify which tables support UPSERT operations.

String sql = "UPSERT INTO hub/dataevents/rowset (dataExtensionId, keys, values) "
           + "VALUES (?, ?, ?)";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "1a2b3c4d-1a2b-1a2b-1a2b-1a2b3c4d5e6f");
    ps.setString(2, "{\"MemberId\": \"38bed58c-9b97-4e95-90bf-8f39e8f539e1\"}");
    ps.setString(3, "{\"FirstName\": \"John\",\"Surname\": \"Doe\",\"RewardsPoints\": 23456,\"RewardsTier\": 3,\"Area\": \"Enfield\"}");
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.error(e);
}

id,errorcode,errormessage,processdata,haserrors
null,null,null,{"keys":{"MemberId":"38bed58c-9b97-4e95-90bf-8f39e8f539e1"},"values":{"FirstName":"John","Surname":"Doe","RewardsPoints":23456,"RewardsTier":3,"Area":"Enfield"}},false

Custom objects may also support the UPSERT operation. Query system.columns using the custom object table name to view columns of the custom object, as well as what actions each column supports.

String sql = "UPSERT INTO customobject_PI_CONTENT (title, availability, uuid, content_id) VALUES "
           + "(?, ?, ?, ?) "
		   + "ON DUPLICATE KEY UPDATE UPSERTFIELDS = uuid";

try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "Test");
    ps.setBoolean(2, true);
    ps.setString(3, "acde070d-8c4c-4f0d-9d8a-162843c10333");
    ps.setString(4, "1");
    ps.executeUpdate();

    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

Metadata Discovery

This section provides examples on how to retrieve table and column metadata using the getTables, getColumns, and getPrimaryKeys methods from the DatabaseMetaData interface. These are essential for discovering database structures.

Tables

The getTables method from the DatabaseMetaData interface can be used to retrieve a list of tables.

This method only retrieves tables that are not write-only.

To get a list of tables that includes write-only tables, query the table system.tables.

try {
    ResultSet rs = connection.getMetaData().getTables(null, null, null, null);
    LOGGER.info("\r\n" + rs.toString());
} catch (SQLException e) {
    LOGGER.severe(e.getMessage());
}

TABLE_CAT,TABLE_SCHEM,TABLE_NAME,TABLE_TYPE,REMARKS,TYPE_CAT,TYPE_SCHEM,TYPE_NAME,SELF_REFERENCING_COL_NAME,REF_GENERATION
null,null,addresses/email,TABLE,null,null,null,null,null,null
null,null,asset/content/assets,TABLE,null,null,null,null,null,null
null,null,asset/content/categories,TABLE,null,null,null,null,null,null
null,null,async/events/status,TABLE,null,null,null,null,null,null
null,null,async/import/summary,TABLE,null,null,null,null,null,null
null,null,async/import/validationresult,TABLE,null,null,null,null,null,null
null,null,async/import/validationsummary,TABLE,null,null,null,null,null,null
null,null,automation/fileTransfers,TABLE,null,null,null,null,null,null
null,null,automation/folders,TABLE,null,null,null,null,null,null
null,null,automation/ftpLocations,TABLE,null,null,null,null,null,null
......

The getTables method returns the following metadata columns:

Column Name	Data Type	Description
TABLE_CAT	String	The catalog that contains the table.
TABLE_SCHEM	String	The schema of the table.
TABLE_NAME	String	The name of the table.
TABLE_TYPE	String	The type of the table (e.g., TABLE or VIEW).
REMARKS	String	An optional description of the table.

Columns

Use the getColumns method of the DatabaseMetaData interface to retrieve detailed information about database columns.

This method returns columns only for tables that are not write-only.

To get columns for write-only tables, query the table system.columns.

try {
    ResultSet rs = connection.getMetaData().getColumns(null, null, "hub/campaigns", null);
    LOGGER.info(rs.toString());
} catch (SQLException e) {
    e.printStackTrace();
}

TABLE_CAT,TABLE_SCHEM,TABLE_NAME,COLUMN_NAME,DATA_TYPE,TYPE_NAME,COLUMN_SIZE,BUFFER_LENGTH,DECIMAL_DIGITS,NUM_PREC_RADIX,NULLABLE,REMARKS,COLUMN_DEF,SQL_DATA_TYPE,SQL_DATETIME_SUB,CHAR_OCTET_LENGTH,ORDINAL_POSITION,IS_NULLABLE,SCOPE_CATALOG,SCOPE_SCHEMA,SCOPE_TABLE,SOURCE_DATA_TYPE,IS_AUTOINCREMENT,IS_GENERATEDCOLUMN,DTS_TYPE
null,null,hub/campaigns,campaignCode,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,hub/campaigns,color,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,hub/campaigns,createdDate,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,hub/campaigns,description,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,hub/campaigns,favorite,16,BOOLEAN,null,null,0,0,null,null,null,16,null,null,null,null,null,null,null,null,null,null,DT_BOOL
null,null,hub/campaigns,id,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,hub/campaigns,modifiedDate,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,hub/campaigns,name,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR

The getColumns method returns the following columns:

Column Name	Data Type	Description
TABLE_CAT	String	The database name.
TABLE_SCHEM	String	The table schema.
TABLE_NAME	String	The table name.
COLUMN_NAME	String	The column name.
DATA_TYPE	Integer	The data type represented by a constant value from java.sql.Types.
TYPE_NAME	String	The data type name used by the driver.
COLUMN_SIZE	Integer	The length in characters of the column or the numeric precision.
BUFFER_LENGTH	Integer	The buffer length.
DECIMAL_DIGITS	Integer	The column scale or number of digits to the right of the decimal point.
NUM_PREC_RADIX	Integer	The radix, or base.
NULLABLE	Integer	Whether the column can contain null as defined by the following JDBC DatabaseMetaData constants: columnNoNulls (0) or columnNullable (1).
REMARKS	String	The comment or note associated with the object.
COLUMN_DEF	String	The default value for the column.
SQL_DATA_TYPE	Integer	Reserved by the specification.
SQL_DATETIME_SUB	Integer	Reserved by the specification.
CHAR_OCTET_LENGTH	Integer	The maximum length of binary and character-based columns.
ORDINAL_POSITION	Integer	The position of the column in the table, starting at 1.
IS_NULLABLE	String	Whether a null value is allowed: YES or NO.
SCOPE_CATALOG	String	The catalog of the table referenced by a reference attribute (null if `DATA_TYPE` is not `REF`).
SCOPE_SCHEMA	String	The schema of the table referenced by a reference attribute (null if `DATA_TYPE` is not `REF`).
SCOPE_TABLE	String	The name of the table referenced by a reference attribute (null if `DATA_TYPE` is not `REF`).
SOURCE_DATA_TYPE	Short	The source type of a distinct type or user-defined `REF` type (null if `DATA_TYPE` is neither `DISTINCT` nor a user-defined `REF`).
IS_AUTOINCREMENT	String	Whether the column value is assigned by Salesforce Marketing Cloud in fixed increments.
IS_GENERATEDCOLUMN	String	Whether the column is generated: YES or NO.
DTS_TYPE	String	Object DTS attribute type.

Primary Keys

The getPrimaryKeys method in the DatabaseMetaData interface is used to retrieve metadata about primary keys for a given table in Salesforce Marketing Cloud.

try {
    ResultSet resultSet = connection.getMetaData().getPrimaryKeys(null, null, "hub/campaigns");
    LOGGER.info("\r\n" + resultSet.toString());
} catch (SQLException e) {
    LOGGER.severe(e.getMessage());
}

TABLE_CAT,TABLE_SCHEM,TABLE_NAME,COLUMN_NAME,KEY_SEQ,PK_NAME
null,null,hub/campaigns,id,1,null

The getPrimaryKeys method returns the following columns:

Column Name	Data Type	Description
TABLE_CAT	String	The catalog name.
TABLE_SCHEM	String	The schema name.
TABLE_NAME	String	The name of the table that contains the primary key.
COLUMN_NAME	String	The name of the column that serves as the primary key for the table.
KEY_SEQ	Short	The sequence number within the primary key.
PK_NAME	String	The primary key name.

Connection Settings

Connection Setting	Type	Default Value	Description
AccountId	String	""	The Account ID option allows you to specify the Account ID which identifies the application making the request.
ApiThrottleRate	Integer	0	The maximum number of API requests a client can make to the server within a specific time period, defined in requests per second.
BulkPollingInterval	Integer	5	Controls how often (in seconds) the driver polls Salesforce Marketing Cloud to check bulk operation status.
CacheExpirationTime	Integer	30	Defines the expiration time for cache. A value of 0 disables caching.
ClientId	String	""	The ClientId used to access Salesforce Marketing Cloud.
ClientSecret	String	""	The ClientSecret used to access Salesforce Marketing Cloud.
ConcurrentWritingThreads	Integer	1	The number of threads for executing operations in parallel. A value of 0 will disable multi threading.
ConnectionTimeout	Integer	30	ConnectionTimeout is the maximum amount of time the program will wait to set up a connection to the Salesforce Marketing Cloud API.
ContinueOnErrors	Boolean	false	Determines if the program continues executing SQL statements after encountering an error.
IgnoreCertificateErrors	Boolean	false	Specifies whether to verify the certificate when connecting to Salesforce Marketing Cloud. If certificate verification is not required, you can set this value to 'true'.
LogFileSize	String	"10485760"	A string specifying the maximum size in bytes for a log file.
LogLevel	String	"INFO"	The logging level for the JDBC driver.
LogPath	String	"./jdbcLogs"	The directory where log files are stored.
OemKey	String	""	The OEM license key.
PathToTokenFile	String	""	The TokenPath specifies the file path where the token for connecting to Salesforce Marketing Cloud is located.
ProxyMode	String	NoProxy	This setting configures the proxy. Allowed values are "NoProxy", "AutoDetect" and "Manual".
ProxyPassword	String	""	The password to be used to authenticate to the proxy.
ProxyServer	String	""	The host of the proxy server.
ProxyServerPort	Integer	0	The port of the proxy server.
ProxyUsername	String	""	The username to be used to authenticate to the proxy.
ResultPath	String	""	The path where the execution result files are saved.
RetryOnIntermittentErrors	Boolean	true	The RetryOnIntermittentErrors parameter indicates whether to retry the connection when it might occasionally fail due to temporary issues.
SaveResult	Boolean	false	The SaveResult parameter indicates whether to save the execution results to a file.
Scope	String	""	Optional. Set the scopes to request when requesting a token. Ensure that the selected scopes are available for your app.
ServiceName	String	""	The ServiceName refers to the name of the service API selected by the user.
ServiceTimeout	Integer	120	The ServiceTimeout is the timeout to receive the full response from Salesforce Marketing Cloud API.
Subdomain	String	""	The Subdomain is used to indicate your specific Salesforce Marketing Cloud account's domain.
Suppress404NotFoundError	Boolean	true	When set to true, if a query results in an HTTP 404 error, a result set will still be created. When set to false, an error is logged instead and no result set is created.
TokenPassword	String	""	The password used to read the token file.

Salesforce Marketing Cloud JDBC Driver

Documentation for Salesforce Marketing Cloud drivers found within JDBC Driver Pack

Salesforce Marketing Cloud

Building the JDBC URL

General Page

Authentication Methods for Salesforce Marketing Cloud

Advanced Settings Page

Using the JDBC Driver

Custom Objects

Executing Statements

SELECT

INSERT

UPDATE

DELETE

UPSERT

Executing Prepared Statements

SELECT

INSERT

UPDATE

DELETE

UPSERT

Metadata Discovery

Tables

Columns

Primary Keys

Connection Settings