March 20, 2003 at 8:12 am
I'm not exactly sure how to approach this, so I'm looking for ideas etc.
First Win2k, SQL2k SP2 + 061 patch, both machines are identical except dasd config.
On the production server I do a nitely backup. Monday I copied the backup to the QA server and restored it. Everything looked good.
The developers them let me know that one table had errors. Some rows had NULL in the manager id field. The table has a self join, it is an employee table, and contains a manager id. Which uses a constraint back to itself, the manager is an employee. Not all rows were screwed up just some ??
Okay restored it elsewhere, same problem. Recopied it and restored it same problem. Copied Tuesdays backup restored it is OK.
Has anyone seen anything like this, or have any ideas what I can do the research what caused it ???
KlK, MCSE
KlK
March 20, 2003 at 8:32 am
Do you backup the database only if its clean (no errors while backups) or Backup with out checking??? Please check that flag in your backup...
I had this kind of problem in 6.5 database earlier.
Hope this Helps!!!!
Regards,
Murali Damera.
.
March 20, 2003 at 8:44 am
No, I don't. My rule is backup (I want a backup, better a bad backup than NO backup), integrity check, then reorgs. So I do not include it as part of the backup process. Note I do "verify the backup upon completion"
But Sundays backup is fine, Tuesdays backup is fine, and the DBCC that ran 30 minutes after the bad backup shows 0 errors.
KlK, MCSE
KlK
March 20, 2003 at 8:50 am
I am not having a clue other than the data inserted on Monday must have been BAD. That nights DBCC must have corrected it.
.
Viewing 4 posts - 1 through 3 (of 3 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