Wednesday, March 21, 2012

Moving SQL Server Off Of A Drive

I need to move my SQL Server files off of a drive that is giving indication
of impending failure.
So far I have moved all of my User Databases and the System Databases
(master, msdb, tempdb, model and even mssqlsystemresource). They have all b
e
relocated to another drive and the server seems to be operating normally.
However, there is a single directory on the original drive that is in use
and can't be moved - MASTER\MSSQL.1\MSSQL\LOG.
Can someone tell me how to change my config to point to a different director
y?
MikeHello,
This is just SQL Server Error Log directory. All you need to do is chnage
the location of the error log directory in the below registry key.
& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\Microsoft SQL
Server\MSSQL.1\MSSQLServer\Parameters]
"SQLArg1"="-ed:\\MSSQL.1\\MSSQL\\LOG\\ERRORLOG"
After that create the new LOG folder and restart the SQL Server. This will
automatically create the Error log in new folder.
Thanks
Hari
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:E1833610-B46A-4B89-A6E9-0A7FF191BE79@.microsoft.com...
>I need to move my SQL Server files off of a drive that is giving indication
> of impending failure.
> So far I have moved all of my User Databases and the System Databases
> (master, msdb, tempdb, model and even mssqlsystemresource). They have all
> be
> relocated to another drive and the server seems to be operating normally.
> However, there is a single directory on the original drive that is in use
> and can't be moved - MASTER\MSSQL.1\MSSQL\LOG.
> Can someone tell me how to change my config to point to a different
> directory?
> Mike|||The log folder is specified with the -e startup parameter. Startup
parameters can be changed using the SQL Server Configuration Manager.
Double-click the desired SQL Server service - it's under the advanced tab.
You'll need to restart the service afterward.
Hope this helps.
Dan Guzman
SQL Server MVP
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:E1833610-B46A-4B89-A6E9-0A7FF191BE79@.microsoft.com...
>I need to move my SQL Server files off of a drive that is giving indication
> of impending failure.
> So far I have moved all of my User Databases and the System Databases
> (master, msdb, tempdb, model and even mssqlsystemresource). They have all
> be
> relocated to another drive and the server seems to be operating normally.
> However, there is a single directory on the original drive that is in use
> and can't be moved - MASTER\MSSQL.1\MSSQL\LOG.
> Can someone tell me how to change my config to point to a different
> directory?
> Mike|||Actually, I had already changed that parameter. But the two responses to my
post sent me if the right direction to the solution.
The problem seems to have been that there is also a startup parameter for
SQLAgent which can only be accessed through the registry
HKEY_LOCAL_MACHINE/Software/Microsoft/Microsoft SQL
Server/MSSQL.1/SqlServerAgent. The parameter is called 'ErrorLogFile'. I
changed that, restarted SqlAgent and all is well.
Thanks to you both for your help.
"Dan Guzman" wrote:

> The log folder is specified with the -e startup parameter. Startup
> parameters can be changed using the SQL Server Configuration Manager.
> Double-click the desired SQL Server service - it's under the advanced tab.
> You'll need to restart the service afterward.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Mike" <Mike@.discussions.microsoft.com> wrote in message
> news:E1833610-B46A-4B89-A6E9-0A7FF191BE79@.microsoft.com...
>|||> The problem seems to have been that there is also a startup parameter for
> SQLAgent which can only be accessed through the registry
That parameter can also be changed from SSMS under SQL Server Agent
properties.
Hope this helps.
Dan Guzman
SQL Server MVP
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:30A628EA-7399-48A0-B66D-12F805928C61@.microsoft.com...[vbcol=seagreen]
> Actually, I had already changed that parameter. But the two responses to
> my
> post sent me if the right direction to the solution.
> The problem seems to have been that there is also a startup parameter for
> SQLAgent which can only be accessed through the registry
> HKEY_LOCAL_MACHINE/Software/Microsoft/Microsoft SQL
> Server/MSSQL.1/SqlServerAgent. The parameter is called 'ErrorLogFile'. I
> changed that, restarted SqlAgent and all is well.
> Thanks to you both for your help.
> "Dan Guzman" wrote:
>

No comments:

Post a Comment