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 - 2002-08-24 : 23:04:15
|
| Muralikannan writes "Dear SQL Team,It would be of great Help, if you could provide me some solution to solve my problem.SQL Server 2000 in Windows 2000 server.I will explain the problem Step-by-step1.We have a Database and since its Log file got filled and no space in the Hard disk even.2. We were unable to do any process. 3. We tried with an unwanted DB existing in the server deleting the Logfile after detaching the same.4. After that we just attached the DB without specifying the Log file name.5. It got restored and we were able to work.6. We tried the same with our earlier mentioned Database which contains Voluminous data.7.Since the Volume is more we had the data file and Log file in two drives.8. After detaching we deleted the Log files from both the drives as we did for the test Database. 9. Afterwards we tried attach it back and it is not allowing us at all.10.We tried some short ways like trying out to restore back, since its not backed up it failed.Pls. suggest a solution so as to handle this. We only have the both .MDF files with us. No .LDF file is available.Awaiting your valuable reply. Thanks in advance.Rgds,Murli." |
|
|
BigRetina
Posting Yak Master
144 Posts |
Posted - 2002-08-25 : 01:57:58
|
| What is the error message that U get when U try to attach the files? |
 |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-08-25 : 03:10:54
|
| Of course you shouldn't have done that. Try to check your recycle bin to see if the .ldf files are still there. Even if you were going to try something idiotic like this, at least you should have backed up the DB first.-Chad |
 |
|
|
royv
Constraint Violating Yak Guru
455 Posts |
Posted - 2002-08-26 : 11:20:52
|
| Try sp_attach_single_file_db. Not guaranteed to work, but it may help you since you did appropriately detach the database, at least that is what I understand from your post.*************************Someone done told you wrong! |
 |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-08-26 : 18:37:30
|
| It won't work, because there were multiple log files.-Chad |
 |
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2002-08-27 : 10:58:17
|
| This is UGLY, but has worked once, when we had a development side problem. Givewn how broken the situation is now, you may want to consider this. As always, no guarantee's etc.Right:1> Copy MDF files elsewhere - somewhere nice and safe.2> Create NEW DB on your server, with EXACTLY the same DB name and filenames, in the same locations3> sp_Detach the new DB4> Copy the original MDF file over your new "dummy" DB.5> sP_Attach the file - that is the orignal MDF, and the new log.We went through the same steps as listed below - the above eventually saved the DB. NOTE Chadmat's point - Any prod work likely to impact the DB should ALWAYS be PRECEEDED by a full backup! Also, get some monitoring procedures in place ! SPace is a critical resouce - you can easily have a DB go suspect on you when you run out of space. Consider putting your your LOGs on different physical drives to your Data files (other threads have good advice on this - look for them). If you ever hit 80% disk used on your DATA or LOG drives, consider yourself out of space, and resolve the issue, be it via archiving, deletion, adding space, etc. etc.Good luck |
 |
|
|
|
|
|
|
|