SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Check Database Integrity taking a long time


Check Database Integrity taking a long time

Author
Message
jayjj
jayjj
Valued Member
Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)

Group: General Forum Members
Points: 56 Visits: 188
Hi Guys,

I have just noticed that in the past few days a Maintenance Plan job that we have on SQL 2012 database seems to be taking a long time to complete. The last job was completed in over 12hrs, however so far i have not been able to pin point exactly what is causing this issue and this job use to complete in 30-60 minutes before. This is not a very large database either as its just 37GB.

From the logs i have worked out that its the CHECK Database Integrity Task which is taking 12hrs, this would start at 01:00AM and Complete at 13:00PM, other task are completed in normal times.

This is the OperationsManager Database within System Center 2012.

Wondering if anyone has an idea of what could be causing this issue.

Thanks
Low Rider
Low Rider
SSC-Enthusiastic
SSC-Enthusiastic (136 reputation)SSC-Enthusiastic (136 reputation)SSC-Enthusiastic (136 reputation)SSC-Enthusiastic (136 reputation)SSC-Enthusiastic (136 reputation)SSC-Enthusiastic (136 reputation)SSC-Enthusiastic (136 reputation)SSC-Enthusiastic (136 reputation)

Group: General Forum Members
Points: 136 Visits: 487
Years ago i had faced a similar issue where the check db took a lot of time to complete.The issue was later found to be with the disk system and we had to move the database to another server.

However this was also accompanied by a reduction in performance of the database.Is your applcation running slowly too?You could get the disk system checked out.
durai nagarajan
durai nagarajan
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1653 Visits: 2775
Is your backup and application using this DB is working fine?

Regards
Durai Nagarajan
jayjj
jayjj
Valued Member
Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)

Group: General Forum Members
Points: 56 Visits: 188
thanks for the reply guys. I have a strong feeling it might be down to a few crashes and restore of the database we had in between this issue, we have made a few changes to assign more memory resource to the database so we are monitoring this and also we think next step is to place the temp database on its own drive.

The crashes we were having were due to the server crashing and corrupting the database as Applications are constantly writing to it, we would then have to restore via a TSM backup because the database would restart in a emergency mode.
SQL Show
SQL Show
Say Hey Kid
Say Hey Kid (671 reputation)Say Hey Kid (671 reputation)Say Hey Kid (671 reputation)Say Hey Kid (671 reputation)Say Hey Kid (671 reputation)Say Hey Kid (671 reputation)Say Hey Kid (671 reputation)Say Hey Kid (671 reputation)

Group: General Forum Members
Points: 671 Visits: 1078
Let us find the root case of delayed checkdb. Since its 37GB, I would suggest to run checkdb in another test machine with your restored 37gb.
ronang
ronang
SSC Rookie
SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)

Group: General Forum Members
Points: 40 Visits: 136
Hi

Check the fragmentation on you db files. Usually after several restores etc. and the fact that it seems to be a heavy write load on this db. Fragmentation can occur quite easily.

Regards,
Ronan
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search