Change location of master database LOG file | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Change location of master database LOG file

Hi, Right after installing SQL 2000 I wanted to change the location of its master database log file .LDF. As I wasnt too smart to change it during installation, I guessed I could do it after installation.. the steps followed (which have led me to failure) are:: 1. Make a copy of the mastlog.ldf file and place it in another location 2. change the parameters at startup and change this parameter
-lc:whatever
ewlocationCopymasterlogfile.ldf (this has failed) 3. try to startup manually with this statement :: sqlservr.exe -m -sInstanceName -lc:whatever
ewlocationCopymasterlogfile.ldf (and new failure) It looks like even if the files are identical (master log files), SQL can’t start the server up with that new location .. Do I miss something? What I am doing wrong? thanks in advance …
Why do you want change the master’s log location? Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
See:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;224071 Make sure you change the paramters first, stop sql server and then copy the master ldf to the new location
That’s exactly what I did
(As I said in the point 2
"
2. change the parameters at startup and change this parameter
-lc:whatever
ewlocationCopymasterlogfile.ldf (this has failed)
"
) And it doesnt work at all, the server isnt able to start …. Changing the log of the master database should be, as I see it, a child’s play, and, in order to have my logs on different disks, thats what i wanted to do, INCLUDING the master database logs … any other suggestion??? ———————— No one travels so high as he who knows not where he is going… {{Oliver Cromwell}}
1.
Verify the startup parameters in the registry as well:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSSQLServerMSSQLServerParameters
(other path for a named instance) SQLArg0 -dd:MSSQLdatamaster.mdf
SQLArg1 -ed:MSSQLlogERRORLOG
SQLArg2 -le:MSSQLdatamastlog.ldf 2.
What are the exact error messages you get when SQL Server can’t start. Should be located both in the SQL logs and the OS event logs.
My question was intended to know if there is any strong reason to change the log path for master database, as the system databases are always small in size and you can achieve as suggested in the KBA. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Good morning all … Well, actually, changing the location of files was an attempt to have control over SQL files and be flexible to change any file to any location. I’m not trying to gain some performance, although I think I prefer to have all the log files on the same location. Point number #2 (and final conclusion)…. DON’T EVER CHANGE THE NAME OF MASTLOG.LDF as SQL is not going to be working … (silly me) We can change location BUT we can’t change its name… So, problem FIXED, and I have learnt a lot about files, I thought Master database files were untouchable! Thanks Argyle for the Registry Keys, it has been very helpful …
Thanks Satya again …

True never attempt to change the system default names for system databases atleast, as you risk the whole setup of SQL server. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>