July 13, 2009 at 10:40 am
I want to restart sql server and it won't start because the start parameters are wrong. I update the startup parameter and click apply and ok. but when i restart it the old parameters are there! HELP!!!!
July 13, 2009 at 11:14 am
Can you post more information about what parameters you're trying to add, what is or isn't working, and the errors?
July 13, 2009 at 11:29 am
-dD:\Data\ATS\FLOR\MSSQL.1\MSSQL\DATA\master.mdf;-eD:\Data\ATS\FLOR\MSSQL.1\MSSQL\LOG\ERRORLOG;-lD:\Data\ATS\FLOR\MSSQL.1\MSSQL\DATA\mastlog.ldf -c -T3608
-c -T3608 is what I was adding. It was to allow the the sqlserver to be brought up so I could detach msdb and repair. That is a whole other problem.
July 13, 2009 at 12:15 pm
-c? What does that do? It's -m for single user mode, -f for minimal config (which I believe is what you need for fixing msdb). Where did you get the -c option from? It's not in Books Online
You need semicolons between the options, not spaces. So what you should have is
-dD:\Data\ATS\FLOR\MSSQL.1\MSSQL\DATA\master.mdf;-eD:\Data\ATS\FLOR\MSSQL.1\MSSQL\LOG\ERRORLOG;-lD:\Data\ATS\FLOR\MSSQL.1\MSSQL\DATA\mastlog.ldf;-c;-T3608
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 13, 2009 at 2:13 pm
Yes, I found this (see below) on social.msdn.microsoft.com web and was going to try this. Since we are on a clustered server, the start command didn't work and that was because one of the nodes were down. didn't realize that both nodes need to be up when you make run the startup at the command prompt. My idea was to do this and then restore the msdb from a backup. Since the command didn't work as described below, I tried modifying the startup command in the config manager and do it that way. I think I don't really have to have sql in single user at all. All I have to do is restore the msdb from backup using sql. MS said I didn't need to detach the msdb database to restore it. I didn't know. This was the first time that I have recoverying a database that was corrupted.
Start SQL Server with trace flag 3608 (to allow you to detach msdb). I did this by shutting down SQL Server and then going to the 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn' directory and from a command prompt doing 'start sqlservr.exe -c -T3608'
Use the master database and detach msdb using "sp_detach_db 'msdb'"
Rename the damaged msdb files (msdbdata.mdf and msdblog.mdf in the 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data' directory)
Run the instmsdb.sql script from the 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install' directory
Shutdown and restart SQL Server normally
However, I'm a little lost on the 2nd step to detatch the msdb. Do I need to start SQL Server again and run the sp_detatch_db command from the MSMS application? I'm guessing because of the last statement. Unfortunately, when I do restart SQL server and attempt to detach the database, I get an error telling me that the Model, MSDB and other databases cannot be detached.
July 13, 2009 at 3:32 pm
Ignore the stuff on the forums, there's an official article on rebuilding MSDB somewhere on the MS site. Might be on MSDN, might be on support.microsoft.com. A search should find it for you.
If you're trying to restore from backup, there's an page in books online on restoring the system databases. Look there first.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply