I have a SQL2K sp2 server on Win2K sp2 srp1
Here is my problem. We have all our data on a SAN that had a failure over
the weekend. When we brought the SQL Server backup, there were several
databases that came back suspect (to make a longer story short, we had to
restore all of these from previous backups). All the db's had no errors show
up in CheckDBs after the recovery. I also moved the msdb database off of
the system C: drive on the server to a drive on our SAN that the SQL Server
box sees as one of it's own drives. I followed the steps to move an msdb
database for SQL2000 and had no errors or problems. I ran a CheckDB and
there were no errors reported and backed up the database. About 20 hours
later, the msdb database corrupted. It was in the process of writing the
backup history for log backups at the time. We run Log B/Us every half hour
on ~ 40 databases on the server. I had to restore the msdb from the
previous backup and the CheckDB showed no errors. About 36 hours later the
msdb database became corrupt again requiring a restore of the db. We can't
find anything wrong w/ the SAN and this is the only db having the problems.

My questions are:
Is there a more extensive check of the databases I can do other than DBCC
CheckDB?
Could we be restoring a bad copy of msdb that a CheckDB does not find?
Could there be more to moving the msdb than the instructions in KB Q224071?
I know how to get the scheduled jobs scripted out & the DTS pkgs out of the
db, what about Maintenance plans - is there a way to script these?

Thanks

Report this post to a moderator