Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We're going to implement a solution based on Change Tracking feature from SQL Server. Before going in production (even after), we'd like to keep track of the overhead the CT will introduce.

Once in production, we'd like to have a counter / event / DMV telling us how much time SQL Server is spending to "keep track" of changes.

Our current (production) installation have tens of (multi-gigabyte) databases (on every instance) and, even if the overhead is low on a single DB, we should measure how much it will be on several Databases.

Thank you Igor.

share|improve this question talks about monitoring Change Tracking, however it neglects to mention anything about performance other than "Change Tracking is lightweight".

It seems you're out of luck...

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.