December 14, 2021 at 3:15 pm
I recently noticed in the logs of one of my 2016 servers that the Change Tracking manual cleanup procedure is running for all databases. I have checked the databases and change tracking is off for all of the databases.
sys.change_tracking_databases and sys.change_tracking_tables are both empty
I tried to just disable the auto cleanup but get a message that change tracking is not enabled.
Anyone else have this odd behavior before?
Dan
If only I could snap my figures and have all the correct indexes apear and the buffer clean and.... Start day dream here.
December 15, 2021 at 4:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
December 16, 2021 at 7:15 pm
I had to dust off my login to reply. We are running many SQL Server 2016 enterprise boxes. Just 2 days ago as well on a brand new virgin install of 2016 cu2 sp17 I've been seeing every 30 min it's attempting the cleanup. We use a Powershell script to install sql + updates and I just completed a solid 30+ installs over the last couple months, but one single box is showing this exact behavior.
I confirmed CT is not enabled anywhere (brand new install).
I think this is a bug. I'd be curious as to you build versions etc. All ours are at 13.0.5888.11
Will update if I find anything else!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply