March 16, 2004 at 2:22 pm
Hello all,
By default, when you install SQL Server 2000, the installation places both the MDF and LDF files for the Master, Model, MSDB, TempDB, Pubs, Northwind and Distribution databases into the location you specified during the install. According to Microsoft Best Practices, you should place the MDF and LDF files onto separate physical disks, where typically the MDF files reside on a RAID 5 disk and the LDF files reside on a RAID 1 disk. Also, the TempDB database (both MDF and LDF) should be placed onto the RAID 1 disk for performance.
I know how to move the TempDB database to a different location, but it is possible to move the LDF files for Master, Model, and MSDB to another physical disk? If so, how do you do it ... sp_detach_db / sp_attach_db or something else?
Thanks,
Jason
March 16, 2004 at 3:05 pm
Well, after some snooping around on Microsoft's Support site, I found what I was looking for. In case you are interested, here's the link explaining the correct procedures for moving System databases.
http://support.microsoft.com/default.aspx?scid=kb;en-us;224071
Jason
March 16, 2004 at 8:29 pm
Something else to consider is also setting up a silent custom installation script using the Sql Server setup templates available on the the setup CD. With these you can develop a automated build process for installing SQL server. This can be a big time saver in managing configuration madness and automating development server rebuilds.
Now something else to consider is don't spend to many resources coding to this scripting techology, because according to a YUKON session I went to they have converted to Microsoft Installer technology finally. This has even more benefits but is a definite bigger learning curve than that of the scripting templates I mention above.
However, It is a win for deployment costs and configuration management issues. Yukon supposed to let you deal with deploying Sql Server with your apps customized for it. That may seem like not much of a big deal. But imagine your app is the admin applet you want to use in your enterprise. You go to install it and it detects that you need your in-house config of sql server set up first. Cool!
I see lots of opportunities to leverage the new .Net Providers and whatever the MSDE engine will be under Yukon.
Peter Evans (__PETER Peter_)
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply