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 |
|
Jhek8866
Starting Member
8 Posts |
 Posted - 2005-01-27 : 19:42:32
|
| Hi Guys,I was trying to move all the system databases(master, msdb, model, tempdb) to another drive and having some trouble. I followed the artichle @ http://support.microsoft.com/default.aspx?scid=kb;en-us;224071Basically this is what I've done so far.- Moved master database successfully- Added the -T3608 as a startup parameter- Restarted SQL Server- Detached Model db, then msdb db- Removed the -T3608 startup parameter- Restarted SQL ServerI can't start up SQL Server at this point. I think I may have mis-understood the steps and should of moved Model and MSDB separately. I'm not totally sure..I've tried to start SQL Server using the SQLSERVR.exe with the flags of -f, -m, and -T3608 with no luck.Thank god this is a development server.. Anybody know what I've done wrong and how I can start up SQL Server again with both msdb and model database detached?Any help would be appreciated.Thanks,Eric |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-01-27 : 19:48:08
|
After you moved master and before you moved model and msdb, did you verify that SQL Server could start? What error are you getting? And just to confirm, you did move model first then msdb, right? I would do each of these separately and making sure that SQL Server can start after each move. That'll at least show you where the problem is.Now that I think more about it, I think it's because you didn't finish the steps for model first before moving on to msdb. You must complete model first, which means removing the startup parameter prior to doing msdb. Take a look at this part in the article for more info:quote:
After you add trace flag 3608, follow these steps: 1. Stop, and then restart SQL Server. 2. Make sure that the SQL Server Agent service is not currently running. 3. Detach the msdb database as follows:use mastergosp_detach_db 'msdb'go 4. Move the Msdbdata.mdf and Msdblog.ldf files from the current location (D:\Mssql8\Data) to the new location (E:\Mssql8\Data). 5. Remove the -T3608 trace flag from the startup parameters box in Enterprise Manager. 6. Stop and then restart SQL Server. 7. Reattach the msdb database as follows: use mastergosp_attach_db 'msdb','E:\Mssql8\Data\msdbdata.mdf','E:\Mssql8\Data\msdblog.ldf'goNote If you try to reattach the msdb database by starting SQL Server with trace flag -T3608, you receive the following error: Server: Msg 615, Level 21, State 1, Line 1 Could not find database table ID 3, name 'model'.
Tara |
 |
|
|
Jhek8866
Starting Member
8 Posts |
Posted - 2005-01-28 : 01:08:15
|
| Yes, I did start SQL Server after I moved the master database. I tried to move both model and msdb at the same time. I'll try to move model first, then msdb. I just need to get SQL Server back up so I can try it :)Thanks,Eric |
|
|
|
rb1373
Yak Posting Veteran
93 Posts |
Posted - 2005-04-11 : 16:00:20
|
| I just moved my databases following the instructions above and now SQL Server Agent won't start. The error I am getting reads: "Coud not start SQLServerAgent on local computer. The service did not return an error. This could be an internal Windows error or an internal service error." Any ideas?Thanks,Ray |
|
|
|
rb1373
Yak Posting Veteran
93 Posts |
Posted - 2005-04-11 : 16:03:19
|
| Doh! I figured it out. I moved the Error Logs in addition to the system databases. I just needed to specify the new error log path in SQL Server Agent properties. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-04-11 : 16:04:36
|
| Check Event Viewer for more information as to why it won't start. Post the related messages/errors in this thread.EDIT: Nevermind.Tara |
|
|
|
|
|
|
|
|
Problem Moving System Databases