RVR-MSSQL-RDBMS-202

1. Issue Summary

   • The error "Failed to get last synchronization version for table" with Error Code: RVR-MSSQL-RDBMS-202 in Rivery's platform indicates a problem with retrieving the last synchronization version of a table in MSSQL using Change Tracking.
   • Initial diagnosis suggests this error is often related to a lack of minimum valid version or missing last synchronization version. This can occur due to improper cleanup or re-initialization requirements.

2. Action Steps:

   • Check Change Tracking Setup: Ensure that Change Tracking is enabled for both the database and the specific table you are working with. You can verify this by running appropriate SQL queries to check the Change Tracking status.
   • Reinitialize the Table: If there is a problem with the minimum valid version or if last_sync_version is not being received, consider reinitializing the table. This involves re-setting the synchronization points and may require initiating migration again from the Rivery interface.
   • Review MSSQL Logs: Examine the logs in MSSQL for any messages related to change tracking, which might provide further insights into the error.
   • Investigate Cleanup Processes: Automated cleanup processes in MSSQL can lead to the loss of synchronization data. Review your database's cleanup schedule and adjust it if needed to ensure it retains necessary data.

3. External References:

   • For further assistance with SQL Server Change Tracking, you can refer to the SQL Server official documentation on Change Tracking to ensure proper configuration and troubleshooting steps.
   • Rivery documentation on SQL Server CDC and Change Tracking for specific configurations and instructions.

If the issue persists or you need further assistance, please open a ticket with Rivery support.