MS-SQL Integrity job failing again and again

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » Data Corruption (SS2K8 / SS2K8 R2) » MS-SQL Integrity job failing again and again

13 posts, Page 2 of 2

««1 2

MS-SQL Integrity job failing again and again

Rate Topic

Display Mode

Topic Options

Author

Message

sql-lover

Posted Wednesday, September 12, 2012 8:03 AM

SSC Veteran

Group: General Forum Members
Last Login: 2 days ago @ 1:19 PM
Points: 226, Visits: 722

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.

Post #1357992

sql-lover

Posted Wednesday, September 12, 2012 12:31 PM

SSC Veteran

Group: General Forum Members
Last Login: 2 days ago @ 1:19 PM
Points: 226, Visits: 722

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?

Post #1358158

Sinfonico25

Posted Thursday, November 29, 2012 4:52 PM

Grasshopper

Group: General Forum Members
Last Login: 2 days ago @ 12:08 PM
Points: 13, Visits: 148

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!!! Crying

), luckily we did not have data loss BigGrin

Hope it help you.

Post #1390916

« Prev Topic | Next Topic »

13 posts, Page 2 of 2

««1 2

Permissions