Just like that puppy you got during the pandemic, your databases hunger for more. And they grow. And occasionally make a mess. I’ll stop the analogy.
Anyhow, it’s worthwhile to occasionally review the tables in a database to see which ones are growing every day, using the most space.
But what if during a review you see the largest table looks like this?
That’s around 24 GB of sweet drive space allocated for 0 records. But…how?
Let me show you how.
If you’ve ever had to implement Change Data Capture (CDC) for a database in an Availability Group, then you know that the CDC jobs don’t really consider the Availability Group. The capture and cleanup jobs created are set up as if the database exists only on a single instance.
And that’s a problem, because I would guess quite lot of databases are in Availability Groups. Maybe even some of yours. If you have this issue, I’ve put together a step-by-step solution in this post.
I know this post is a little long compared to others here, but I’ve tried to be thorough to save you headaches.
Powered by WordPress & Theme by Anders Norén
By continuing to use the site, you agree to the use of cookies. more information
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.