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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-06-29 : 09:39:03
|
| Ralph writes "A series of first-time mistakes led to this mess.First, I had trouble reformatting the drive before setting up SQL Server 7.0 (now with SP2) with NT 4.0 (SP6). The C: drive ended up with too little space. The rest went to other drives.Then I put SQL Server on the C: drive. Oops. I also thought I was going to put the data files on another drive, but I apparently missed the step for that. Oops.My C: drive ran out of space. I had 2 backup copies of my monster SQL database, so I moved it in order to be able to use my C: drive. Oops.When I moved it back, it wouldn't work. It says the log is corrupted.The restore won't work. At first it said I had insufficinet disk space (surprise), then I moved a folder (not SQL-related) for room. Then I got "MS SQL-DMO (ODBC SQLState: 42000) An internal consistency error occured." This happens with or without "Force restore over existing database" checked.As a side note, somehow I ended up with a file mydbname_log.ldf that's 1.3 GB, 5 times the size of the MDF file, in my backup directory on another drive. It's a 3-week old file, so I must have created it during a backup. I have no such file elsewhere.Have I created a classic horror story to scare new DBAs into, say, reading the book before experimenting? That's a rhetorical question.What can I do to be able to use my database again? If I un-install SQL 7 and reinstall it on a drive that has sufficient space, am I more likely to be able to use the database again or will I only make things worse?" |
|
|
|
|
|
Database moved