Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
FileAnt
Starting Member
3 Posts |
 Posted - 2009-03-11 : 21:45:00
|
What can cause this. Harddisk?All the dates should be the same. It is sqlserver 2000 sp4 p.s. I don't have access to the machine, but I was told the error happened last month so it used to be correct. Oh, and they rebuild the indexes every night... not something I would do as I read somewhere it was risky. |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2009-03-11 : 22:03:07
|
| Rebuilding indexes isn't risky. There have been bugs in the past but there shouldn't be anything in SP4.Can you get them to run the following on the database:DBCC CHECKDB (yourdb) WITH ALL_ERRORMSGS, NO_INFOMSGSand post the results.Yes, the IO subsystem can cause this, rarely also faulty memory.Do you have a backup you can restore somewhere else to figure out the correct date to manually update (assuming that's the only corruption)?Paul S. Randal, Managing Director, SQLskills.com (www.SQLskills.com/blogs/paul)SQL Server MVP, Contributing Editor of TechNet MagazineAuthor of SQL 2005 DBCC CHECKDB/repair codeAuthor & Instructor of Microsoft Certified Master - Database course |
 |
|
|
FileAnt
Starting Member
3 Posts |
Posted - 2009-03-11 : 22:43:36
|
| Someone already fixed the date last month... I was just after some ideas as the internet seems to not have much on this and this forum seems like a good spot.CHECKDB could not fix the error.REBUILD indexes had some error about "Keys out of order" .. just a symptom of the bad date.Probably a weak 80Gig drive in the heat wave or somethingGood to hear about Rebuilding indexes being OK... last time I read about it being a slight risk was probably a few years back now. (something about dropping an index during an update being dangerous.. especially during replication)Thanks |
|
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2009-03-12 : 11:07:30
|
| Right - CHECKDB won't ever fix invalid value errors.Here's a link for you: [url]http://www.sqlskills.com/BLOGS/PAUL/post/Search-Engine-QA-26-Myths-around-causing-corruption.aspx[/url]Paul S. Randal, Managing Director, SQLskills.com (www.SQLskills.com/blogs/paul)SQL Server MVP, Contributing Editor of TechNet MagazineAuthor of SQL 2005 DBCC CHECKDB/repair codeAuthor & Instructor of Microsoft Certified Master - Database course |
|
|
|
|
|
|
Corrupt DateTime