How do you know that no DML is affecting the table?
Did you add a DML trigger that writes to a log table, and it was empty the next day?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
SQL Server 2017 CU 24
Table partitioned on a daily value
Incremental statistics show a modification_counter despite no DML impacting the table, how or why is this occurring.
I am trying to set up a periodic job that will run incremental statistics on large tables with just inserted data but the sys.dm_db_incremental_stats_properties job shows a modification_counter of the last insert repeatedly despite the fact that the stats have been run and reset the modification_counter to 0
Any help would be appreciated.
Thanks,
James
How do you know that no DML is affecting the table?
Did you add a DML trigger that writes to a log table, and it was empty the next day?
Hi @James Tuggey ,
Agree with Erland. Suggest you to capture this and share us the result. For creating DML trigger, please refer to MS document to get detail steps.
If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar thread.