January 15, 2010 at 9:29 am
Our SAN failed briefly while they were doing some work with it, caused several of our apps to go offline as the database servers were unable to access their files on the SAN.
Any best practices/suggestions on what we should do to ensure our database files are in good working order?
Thanks.
January 15, 2010 at 9:36 am
Run this on all databases that were on the SAN
DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 15, 2010 at 9:40 am
Thanks, anything other than check database that I should do, or does that pretty much over it?
January 15, 2010 at 9:52 am
That will check every page in the database for corruption, check the schema, check the allocation information. If there's any form of corruption in the database it'll pick it up (and if it doesn't nothing else will either)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 4, 2010 at 6:27 pm
You might want to check if any jobs/maintenance plans that were running at the time failed. They will need to be investigated and run again.
Joie Andrew
"Since 1982"
February 4, 2010 at 6:28 pm
Just to make sure, are any of your databases in replication?
Joie Andrew
"Since 1982"
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply