The following section lists important best practices for using the JDBC driver. You can find additional information in Section 6.0, Configuring the JDBC Driver.
Security/Performance:
For performance and security reasons, run the driver remotely on the database server whenever possible. Be sure to enable SSL encryption between the Identity Vault and the Remote Loader service.
You should enable SSL encryption for third-party drivers whenever the JDBC driver is not running remotely on the database server. For information on the security capabilities of supported third-party drivers, see Third-Party JDBC Drivers.
In a production environment, turn off tracing.
Other:
For direct synchronization, prefix one or more view column names with “pk_” (case-insensitive).
For both direct and indirect synchronization, use different primary key column names between logical database classes.
Delimit (double-quote) primary key values placed in the event log table_key field if they contain the following characters: , ; ' + = \ " < > This caution is usually an issue only if the primary key column is a binary type.
When an Identity Vault is the authoritative source of primary key values, GUID rather than CN is recommended for use as a primary key. Unlike CN, GUID is single-valued and does not change.
From publication triggers, omit foreign key columns that link child and parent tables.
If primary key columns are static (they do not change), do not include them in publication triggers.
Place the jdbc:type="query" attribute value on all embedded SELECT statements. Place the jdbc:type="update" attribute value on all embedded INSERT, UPDATE and DELETE statements.
To avoid issues that araise when you run a sql query that has a reserved word as a column name, specify a fully qualified name for the column.
For example, when you use as a column name under table, being is a sql keyword, your query might not be properly executed. To avoid this, specify a fully qualified name (<Tablename>.<Columnname>) for the column.