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


MS-SQL Integrity job failing again and again


MS-SQL Integrity job failing again and again

Author
Message
sql-lover
sql-lover
SSCarpal Tunnel
SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)

Group: General Forum Members
Points: 4633 Visits: 1930
Well,

I restored the database on a different server and same MS-SOL flavor (or almost) but it's the best I can do, I have no more available servers and space for that.

It took a while, but it's there and NOT in a suspect state; database is open and available. That's good!

Now I am running (on that standby server) a DBCC CHECKDB and waiting for results. Crossing fingers! Unsure

I still believe is not data corruption, but if DBCC command via console gave errors (hopefully it will not) here's what I am planning to do;

Run this


DBCC TRACEON (3604, -1)
GO
DBCC PAGE('MyDatabase', 1, 12345, 3)
GO


Where 12345, would be the corrupted data page? Hopefully it won't be a Clustered Index. If it's a non clustered Index, drop it and recreate it. Otherwise, go back a few weeks and check backups.

I do not know if I should re-run the DBCC command via Maintenance Plan if the DBCC command via console gives errors. That may be the issue, and not real data corruption.
sql-lover
sql-lover
SSCarpal Tunnel
SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)

Group: General Forum Members
Points: 4633 Visits: 1930
It took 4hrs to complete ... but no errors ...


CHECKDB found 0 allocation errors and 0 consistency errors in database xxxxxx


I guess that next (and last step) is creating a SQL job and invoke DBCC from there?
Sinfonico25
Sinfonico25
Valued Member
Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)

Group: General Forum Members
Points: 55 Visits: 167
I had a similar problem. The only way, to stop it, was: doing a data migration to a database created directly on the instance with the compatibility level according to the sql server version (because I recovered from MSSQLS 2005 to MSSQLS 2008 R2 and appeared me "suspect" 3 times in one week!!! :cryingSmile, luckily we did not have data loss :-D

Hope it help you.
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