SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Moving master LDF to log drive


Moving master LDF to log drive

Author
Message
SkyBox
SkyBox
SSC Eights!
SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)

Group: General Forum Members
Points: 838 Visits: 737
I normally leave sys db's in the default location (not tempdb). However, I have a production 2008 instance, where the sys db log files (.LDF's) reside on my data file drive/LUN.

When testing on a SQL 2012 box I was able to alter/modify the files and move them fine with the exception of the master.ldf file. I had to change the path on the startup params w/in SQL config manager.

Everything restarted and moved ok. Is there anything I am missing or any "gotcha's" with this move? Will this affect upgrades or service packs?

Thanks
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53223 Visits: 17672
There's little point moving the masters log file. Best to always keep the master files in one location as with model and msdb too

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
SkyBox
SkyBox
SSC Eights!
SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)

Group: General Forum Members
Points: 838 Visits: 737
Perry Whittle (9/18/2012)
There's little point moving the masters log file. Best to always keep the master files in one location as with model and msdb too

I'm not really seeing any activity on those log files, so I'll follow your advice.
John Mitchell-245523
John Mitchell-245523
SSC-Dedicated
SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)SSC-Dedicated (34K reputation)

Group: General Forum Members
Points: 34187 Visits: 16649
SkyBox (9/18/2012)
Everything restarted and moved ok. Is there anything I am missing or any "gotcha's" with this move? Will this affect upgrades or service packs?


No, it won't affect anything like that. If your system databases data files are on your system drive (for example in C:\Program Files\Microsoft SQL Server\....) then I would recommend moving them to a drive dedicated to database files. This ensures that SQL Server doesn't get choked by growth of things like application logs, and conversely that any growth of your system databases won't eat up all the disk space that the operating system should be using. You may find that your msdb database grows quite large, especially if you don't control your job, backup and maintenance plan histories.

John
SkyBox
SkyBox
SSC Eights!
SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)

Group: General Forum Members
Points: 838 Visits: 737
John Mitchell-245523 (9/20/2012)
SkyBox (9/18/2012)
Everything restarted and moved ok. Is there anything I am missing or any "gotcha's" with this move? Will this affect upgrades or service packs?

then I would recommend moving them to a drive dedicated to database files.
John


My sys database files are properly located on my data file drive (not CSmile. It's my system database transaction log files that also reside on that data drive rather than the dedicated log drive.

The only reason I started the post is because one reads/writes sequentially and the other randomly, but there's not much activity that I can see on those sys log files so it shouldn't be affecting the data drives performance.
EdVassie
EdVassie
SSChampion
SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)

Group: General Forum Members
Points: 13811 Visits: 3894
There are no performance or integrity advantages in moving the locations of Master, Model, and MSSystemResource databases.

If you make heavy use of msdb then consider moving its files to where you store your user databases, otherwise leave that alone also.

Leaving these files in their original locations may look 'untidy', but many people run into problems when trying to move them. Also, Microsoft have a poor track record of making SPs and CUs work when these files are moved, but SQL 2008 R2 onwards (so far!) has been OK. A DBA should have more important things to do than put their system at risk doing work that gives no advantages.

Original author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005. 14 Mar 2017: now over 40,000 downloads.Disclaimer: All information provided is a personal opinion that may not match reality.Quote: When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist. - Archbishop Hélder Câmara
SkyBox
SkyBox
SSC Eights!
SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)SSC Eights! (838 reputation)

Group: General Forum Members
Points: 838 Visits: 737
EdVassie (9/21/2012)
There are no performance or integrity advantages in moving the locations of Master, Model, and MSSystemResource databases.

If you make heavy use of msdb then consider moving its files to where you store your user databases, otherwise leave that alone also.

Leaving these files in their original locations may look 'untidy', but many people run into problems when trying to move them. Also, Microsoft have a poor track record of making SPs and CUs work when these files are moved, but SQL 2008 R2 onwards (so far!) has been OK. A DBA should have more important things to do than put their system at risk doing work that gives no advantages.


Thanks for the advice - this is why I like to research something before I change it...
- Win
- Win
SSChasing Mays
SSChasing Mays (612 reputation)SSChasing Mays (612 reputation)SSChasing Mays (612 reputation)SSChasing Mays (612 reputation)SSChasing Mays (612 reputation)SSChasing Mays (612 reputation)SSChasing Mays (612 reputation)SSChasing Mays (612 reputation)

Group: General Forum Members
Points: 612 Visits: 707
Thanks

Cheers,
- Win
"Dont Judge a Book by its Cover"
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search