I am researching how to convert some physical tables to memory-optimized tables.
But these tables have timestamp column.
This data type is not supported in MO. How to replace it? Now these columns used in app to compare and check if another app changed the row.
1 Answer
I am not quite sure why you would want rowversion in a MO table. Have you run the Memory Optimization Advisor?
You could try using a trigger to update a column with a sequence or NEWID().
-
Because the timestamp columns already are in tables and used in apps. Advisor said me ts is not supported– ZedZipCommented Jul 10, 2024 at 13:18
-
Then why do you want to make this a MO table? Are you sure of the use case?– AardvarkCommented Jul 10, 2024 at 13:41
-
I am searching ways to improve performance of our database. It works on SQL 2022, has not so large size but bad performance on some queries– ZedZipCommented Jul 12, 2024 at 7:12
timestamp
as used here, is the deprecated (and unfortunately named) synonym forrowversion
. If so, ongoing discussion on the merits of datetime et al are largely irrelevant.