RVR-MSSQL-RDBMS-206

1. Issue Summary

   • The error code RVR-MSSQL-RDBMS-206 indicates an issue with the MSSQL Data Connector unable to retrieve the keys for a specified table. This can often be attributed to problems such as incorrect table meta-information, absence of primary or composite keys, or issues with the Change Tracking or Cleanup processes within SQL Server【4:1†Rivery Documentation 202408 (2).pdf】.

2. Action Steps:

   • Verify Key Existence: Ensure that the table in question has primary keys or composite keys defined. Lack of keys will prevent Rivery from conducting operations that require them.
   • Change Tracking: Check if Change Tracking is enabled for the database and the specific table. You can do this by running queries against the sys.change_tracking_databases and sys.change_tracking_tables to verify the change tracking settings【4:17†Rivery Documentation 202408 (2).pdf】.
   • Inspect Cleanup Processes: Automated cleanup of the Change Tracking data might be happening too frequently, leading to data removal before full synchronization. Monitor and adjust these processes if necessary【4:6†Rivery Documentation 202408 (2).pdf】.
   • Review Logs: Analyze the MSSQL server logs for any errors or messages related to the failure in retrieving keys. These logs can offer insights into why the keys are not obtainable.
   • Reinitialize Table: If change tracking is a factor, consider reinitializing the table from the Rivery console to reset synchronization and potentially resolve the issue【4:5†Rivery Documentation 202408 (2).pdf】.

3. External References:

   • For additional troubleshooting on SQL Server issues, you can refer to the official Microsoft SQL Server Documentation.
   • Detailed Rivery documentation specifics can be found here for further setup and configuration guidelines specific to using MSSQL with Rivery.

If the issue persists or if these steps do not resolve the problem, please open a ticket with Rivery support to receive more specialized assistance.