Comments
4 comments
-
Another note: RR is aware the database schema has HISTORY_RETENTION_PERIOD = 7 YEAR but it does not generate code with that parameter. Adding that parameter manually in the migration script results in a syntax error. Thanks!
-
I did the same thing with SQL Change automation. It does a little better, as it captures History_retention_Period = 7 Years for 1 table out of 3 system-versioned tables in my database.
-
Could you please show us the create table scripts for the 3 tables?
-
It turned out that our team turned off system versioning on the other 2 tables and turn system versioning back on without the retention period parameter.
So SQL Change automation capturing 1 retention period parameter for 1 out of 3 system versioned tables is correct since the database itself has only 1 parameter specified.
Thank you for your time and assistance.
Add comment
Please sign in to leave a comment.
1. the generated script dropped the 'HISTORY_RETENTION_PERIOD = 7 YEAR' of all the tables.
2. When I edit the generated script to add HISTORY_RETENTION_PERIOD = 7 YEAR back in, I receive a syntax error.
Is anyone else seeing the same issues? Thanks!