October 23, 2014 at 7:50 am
We have restored a database to SAN storage as part of a migration. A scheduled run of DBCC CHECKDB failed after the restore. Repeated runs of DBCC CHECKDB are returning different results. Each run returns consistency errors, but the consistency errors show up on different pages and allocation units. When the database is restored to local storage, DBCC CHECKDB comes back clean. That points me to an issue with the SAN, but I am very confused by the changing DBCC CHECKDB results. Has anyone seen behavior like this before?
Thanks,
Frank
October 23, 2014 at 8:15 am
Additional information:
The database is 423GB.
It contains one data file, one fulltext file, and one log file.
Three smaller databases on the SAN do not show corruption.
Let me know if additional information is needed.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy