Choose DB File locations during install?

  • Hey folks!

    Just working on some new installs and generally we like to separate out the .mdf and .ldf files into separate drives for performance reasons.  I've been digging around and found out how to do it after you've done the install (http://msdn2.microsoft.com/en-us/library/ms345408.aspx), but I'm wondering if there's a way to do that right from the start in the install wizard?

    Is there a way I can set the .mdf files to install to one path and .ldf files to install to a different path? 

     

    Thanks!

  • If you are using the SSMS...

    right click [Databases] new database

    in the new database wizard schroll to the right in the [Database files] area to the Path entry.

  • Ah, yeah, I know about that.  I'm more worried about all the system DB's like master, model, etc. that get installed during the original install.  They can be moved after the fact, but it's a pain.  Be so much easier if you could just set default locations for all that during the actual install.

  • On the Setup Screen of SQL Server 2005 ==> Components to Install ==> Select "SQL Server Database Services" And Click on Advanced.

    Expand Database Services ==> Data Files and Click on Browse.

    Specify  the path where you want to have the system databases and this should work.

    Thanks

    Sumit Sarkar

     

  • For other new user Dbs you can make the default path by configurin that in config manager.

    Cheers,
    Sugeshkumar Rajendran
    SQL Server MVP
    http://sugeshkr.blogspot.com

  • When we installed SQL 2005, we were unable to split the .mdf and .ldf files.  We could change the base location of the DBs, but couldn't split up the files.  I've tried that with Developer on my own PC to be sure.

    You can, however, use the ALTER DATABASE command afterwards to split them up.  Then stop the services, copy the .LDFs over to their new location and restart the services.

    If anyone finds a way of splitting the files during install, let me know.  I've tried everything I can think of and can't find the method, if one even exists.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Alright, thanks for the info guys!  That will at least get me half way there by putting the mdf's in another path.  I'll have to just move the .ldf's after that.

    What really causes problems is the mssqlsystemresources DB.  If that's not done right, you have all sorts of issues patching and such down the road.

     

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply