• Added support for Batch Processing for the following operations:
  • Create (45679)
  • Delete (46763)
• Added support for SQL tables with names that start with numbers. (45682)
• Validated support for Microsoft SQL Server 2017: Enterprise, Standard, and Express. (48409)

Addressed Issues

• When using Microsoft SQL Server as a target datastore for Replication Service Solutions, the most recent date in the SCRIBE_MODIFIEDON target field for each table is used as a filter to query the corresponding source entity for new, changed, and deleted.This may result in some deleted records being reprocessed in cases where the date in the SCRIBE_DELETEDON target field is newer than the most recent date in the SCRIBE_MODIFIEDON target field. (52181)
• Improved retry logic when the Connector receives an inbound message to be processed by a Request/Reply Map to solve intermittent exceptions similar to the following: The connection is broken and recovery is not possible. The connection is marked by the client driver as unrecoverable. No attempt was made to restore the connection. (46610, 44134 / Case # 57390)
• When a Replication Solution is running, if the target table is missing a required primary key constraint, the table is recreated before the associated records are replicated. (15512 / Case # 79680, 79688)
• Using the Create Block with Microsoft SQL sometimes returns more than one success message per record, which was generating an Error Number: 0 error. (36974, 38071 / Case # 52419, 53406)
• When using Windows Authentication via a group to access Microsoft SQL Server, the default schema could not be accessed preventing the Connector from retrieving metadata. (43462 / Case # 57408)
• Using the Query Block to access a Microsoft SQL Server database was locking third-party systems out of that database until the TIBCO Scribe® Online Agent was stopped. (44479 / Case # 56080, 58688)
• The TargetTimeout setting on the Connection configuration dialog used the default value of 30 seconds regardless of the actual setting. (D52387 / Case # 61295)
• When the server time on the source datastore and the server time on the Agent server differed, some records were not Updated or Deleted during the execution of a Replication Solution. (D32222, 48928, / Case # 75482, 75489)
• Replication Solutions were attempting to alter the decimal precision on float data types resulting in reduced performance for large datasets. (D49125, D48970 / Case # 60150)