April 25, 2002 at 9:18 am
Have a new SQL Server 2000 here running Sun Accounts. The consultant that installed the server did so without any help. It appears that he installed the Log and Data files on the same physical device. The another consultant came along and installed an older version for testing on the same server and put the files on the SAME DISK DRIVE. Then another consultant ran a big SQL Update job last night, creating a massive log file, and brought the whole server down!
I`m currently trying to restore the database after creating some disk space.
Jeez, how do you avoid such stupidity?!
Andy.
April 25, 2002 at 10:06 am
You shoot consultants from other companies coming in to mess with your server on site, dead or alive. Then when you get thru laughing about what you were thinking should be done you tell them you have to be involved and that anything they break they must fix or pay for the time to fix it as they should have tested and known the effects beforehand.
But to clear your problem the easiest way look in BOL at sp_detach_db and sp_attach_single_file_db as then you can delete the log file in the middle of these 2 steps freeing you space quickly. I would then consider moving the log files at minimum when time permits to their own drive preferable.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 25, 2002 at 10:28 am
Bad news.
Tried a database restore but it bombs out about 6% thru. Some problems with the log file at a certain point. Tried detaching it, and then reattaching it, but get a similar error.
Is there anyway of clearing the log file and then attaching it.
Turns out no one backup up the machine, so I can regress back to an old log file either.
Andy.
April 26, 2002 at 4:05 am
Tried that.
It won`t let me attach the old MDF file after renaming the corrupted LDF file.
Andy.
April 26, 2002 at 4:25 am
Try sp_attach_single_file_db if you have only one log file. From BOL
quote:
When sp_attach_single_file_db attaches the database to the server, it builds a new log file and performs additional cleanup work to remove replication from the newly attached database.Use sp_attach_single_file_db only on databases that were previously detached from the server using an explicit sp_detach_db operation.
Use sp_attach_single_file_db only on databases that have a single log file. Do not use this stored procedure on databases that have multiple log files.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 26, 2002 at 4:58 am
The old log file seems to be corrupt. I tried using that SP to attach the MDF file alone as it says on the MS site that it will create a new LDF file. However, this doesn`t work either. Although it says it should. Problem is though it says it should work in SP2, this server is SP 1 and I can`t upgrade it!!!
Arrghhh!
Andy.
April 26, 2002 at 5:11 am
Ok can you do sp_attach_db to reattch both the MDF and log file (name back first). Then do from QA sp_detach_db rename the log file and use sp_attach_single_file_db. Also I looked and found no issues with this and have used many times here with SP1. What article were you looking at? Also how big is the DB and do you have a test server you can try the DB attaching with the single file on? I would also be after a consultants head over this.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 26, 2002 at 7:13 am
Hi Andy
You've got the best advice already. All I can offer is some sympathy. Your use of the word Idiot is very restrained. Hooligan would fit the bill better (before you get to Anglo Saxon).
Best of luck, I hope it all pans out and you get the Weekend to recover.
I have found it is easy to please a great many people all of the time if you do exactly what they want. Harold Macmillan 1961
I have found it is possible to please all of the people all of the time if you do exactly what they want. Harold Macmillan 1961
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply