There might be a delay in updates to the SAS Digital Marketing tables. This delay might be more noticeable when the broadcasts are of a high volume (for example, 100,000 or more e-mail recipients).

Performance and general stability of the system might also be badly affected.

Click the Hot Fix tab in this note to access the hot fix for this issue.

After you apply the hot fix, the following advanced server properties are available to control the concurrent behavior of the JDBC update process for response, reply, audit, and link tables:

1. EnableParallelJDBCUpdate: Enables the parallel processing of the SAS Digital Marketing response, replies, audit, and link records when set to true. The default value is false. This property should be set to true when the response, replies, audit, and link tables are stored in a database that supports concurrent table update. Note that SAS data sets do not support concurrent updates to a table and are not recommended for use as the SAS Digital Marketing tables. See SAS Note 47241, "The SAS Digital Marketing response table or opt-out table might lose information" for additional information.
2. ParallelJDBCUpdateThreads: Specifies the number of threads that are used for parallel JDBC updates. The default value is 5. You can increase this by a small number, but it must remain significantly less than the c3p0 maximum connection pool size. Otherwise performance will be impacted elsewhere.

Add these new advanced server properties in SAS Digital Marketing Studio. Then restart the bess.war files, the sdm.war file, and SAS Digital Marketing Server.

Operating System and Release Information

A fix for this issue for SAS Digital Marketing 6.1_M1 is available at: