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 |
|
cjp
Yak Posting Veteran
69 Posts |
 Posted - 2011-09-27 : 11:36:05
|
| I am running sqls 08 64-bit on W7 x64 ProRecently, my main box had an upgrade - cpu and an extra hard drive. For a few weeks, everything was fine and then I noticed data corruption when an attempt to build a new index bombed out. On further examination, several tables were affected but not all of them. My backups restore perfectly on other computers (checkdb() runs clear) but not on my main box - where there is a long list of errors.I have restored my databases from sqls 2005 to sqls 2008. Historically, this has always gone well but I am wondering if there are any known issues when migrating databases into 2008.Manufacturer checks on hard drives and memory have (so far) come up clear but I suspect that hardware problems are the likely explanation for the problem but I would like to know if there are known issues when restoring earlier objects into sqls 2008.I have struggled to find clear guidance on the web - hence posting this request.Thanks.Chris |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2011-09-27 : 12:01:14
|
| No issues in restoring 2005 -> 2008. Corruption is a hardware problem typically. Mostly IO subsystem, occasionally memory.--Gail ShawSQL Server MVP |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2011-09-27 : 13:01:29
|
| "are there any known issues when migrating databases into 2008."here's some things you should consider doing when upgrading:http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=138230but "not" doing them won't corrupt your database, it might run slowly, or it might not be optimally configured.Having said that, that thread includes some additional checks that you can make, which might reveal that your SQL 2005 database did had some issues before migration. |
|
|
|
cjp
Yak Posting Veteran
69 Posts |
Posted - 2011-09-28 : 02:32:48
|
| Thanks for your replies and guidance.I have done most of what you advise: the databases were restored clean from verified backups into a new installation of SQLS 2008, and all databases were known to be OK (I have used the same backups to restore to two other computers, and they all generate perfect databases - no problems when I run checkdb). I have also run dbcc updateusage: this makes some minor changes but checkdb still throws up plenty of problems afterwards.I always use the same collation - and check that the correct collation default is set.The solution is proving very elusive: the memory is ecc memory and the cpu is an Intel Xeon X5690; the hard disks are very expensive Seagate SCSI devices - I have never had problems with these components before but I agree that this is likely to be hardware-related, even if tracking down the problem is proving difficult.Chris |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2011-09-28 : 03:36:53
|
| " I have also run dbcc updateusage: this makes some minor changes"I believe (but haven't verified it) that the issues with the Counts being inaccurate have been fixed in SQL 2008, so you should only get "adjustment" of the figures the first time you Update Usage on SQL 2008, and thereafter it should not change.Certainly, in my experience, the Counts frequently changed when using Update Usage on SQL 2000 (hence the first time Update Usage was run on SQL 2008 there was likelihoods that the Counts would be adjusted |
|
|
|
|
|
|
|
|
strange issue with intermittent data corruption