| Author |
Topic |
|
pareshmotiwala
Constraint Violating Yak Guru
323 Posts |
 Posted - 2009-12-11 : 23:05:00
|
| We have windows 2003, sql 2005.We just expanded the drive containing .ldf files.Before doing that we had copied the files over as a safety to another server.When the drive came up(expanded from 72 GB to 300 GB), we copied the files back from the other server to the current location.We tried to bring up the sql service, and all databases show as corrupt. Any ideas?PareshRegardsParesh MotiwalaBoston, USA |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
pareshmotiwala
Constraint Violating Yak Guru
323 Posts |
Posted - 2009-12-11 : 23:21:35
|
| the sql was indeed stopped completely when we copied them over.recovering from backups may be a problem as we have about 25 dbs.RegardsParesh MotiwalaBoston, USA |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
pareshmotiwala
Constraint Violating Yak Guru
323 Posts |
Posted - 2009-12-11 : 23:38:45
|
| yes they are in suspect modeRegardsParesh MotiwalaBoston, USA |
|
|
|
pareshmotiwala
Constraint Violating Yak Guru
323 Posts |
Posted - 2009-12-11 : 23:57:04
|
| u there?RegardsParesh MotiwalaBoston, USA |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-12-12 : 04:06:42
|
| This isn't a help desk and there's no SLA on replies. We reply when and as we have spare time. If you need urgent assistance, I suggest you contact Microsoft's customer support,Query sys.databases, check the column state_desc for all the databases. Open the SQL error log, look for all the messages relating to these DBs. Post them here (if you're not sure post the entire error log)--Gail ShawSQL Server MVP |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
pareshmotiwala
Constraint Violating Yak Guru
323 Posts |
Posted - 2009-12-14 : 16:08:27
|
| Tara, thanks for your help. I did not have to restore the databases. But I did the following since there was no extra activity on the databases sicne we last shut them down.I first put them in emergency mode, then into single user mode, then run dbcc with "allow data loss" and then back into multi user mode. put them all back into Full mode. Scary scenes, but we survived. This week we were planning to do the same with the drive having the .mdf files but have chosen to abstain from it...We met today to move the entire server to a VM environment.Thanks for your help once again and wish that other members were as obliging and nice as you.RegardsParesh MotiwalaBoston, USA |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-12-15 : 04:42:57
|
quote:
Originally posted by pareshmotiwala
I first put them in emergency mode, then into single user mode, then run dbcc with "allow data loss" and then back into multi user mode. put them all back into Full mode. Scary scenes, but we survived.
You do realise that you may well have lost data? Repair with allow data loss is an absolute last resort when there's no other solution. Restoring from backup is the recommended solution for most forms of corruption. Only if there's no backup should a repair be considered.quote:
Thanks for your help once again and wish that other members were as obliging and nice as you.
Anyone in particular that's aimed at?--Gail ShawSQL Server MVP |
|
|
|
|
All Databases corrupt