I can't see that it has any impact. DBCC is basically a readonly operation. The one write operation it does is that it creates a hidden database snapshot, and it is the snapshot it examines. If you kill DBCC it should remove the snapshot, I think. But I need to add the caveat that I have not tested.
What is the impact If I stop dbcc checkdb job part of alwayson secondary?
What is the impact If I stop dbcc checkdb on secondary server in middle, dB is in huge size. Is dB went to kill or rollback state any impact to alwayson synchronization issues because of stopping the job?
2 answers
Sort by: Most helpful
-
-
MikeyQiao-MSFT 560 Reputation points Microsoft Vendor
2024-04-29T02:12:23.5566667+00:00 Hi,nasar babu
DBCC CHECKDB does consume some resources when running, but this is limited to local system resources, such as the I/O system and CPU resources. Pausing DBCC CHECKDB might offer some performance benefits to the synchronization job.
As Erland mentioned, DBCC CHECKDB creates an internal snapshot database. Secondary replicas are typically used for read operations and backups, not for handling production workloads. Synchronization occurs over a separate network connection and is primarily influenced by network bandwidth and latency, not by resource usage on individual replicas.
If you're concerned about the impact, it's recommended to use SSMS to view the Availability Group's dashboard or other methods to monitor the synchronization performance of the Availability Group.
Best regards,
Mikey Qiao
If the answer is the right solution, please click "Accept Answer" and kindly upvote it.