Get Data, Log, Backup, and Binn Directory (SQL Server 2005)

  • Comments posted to this topic are about the item Get Data, Log, Backup, and Binn Directory (SQL Server 2005)

  • Hello,

    Nice script. I've tested it a SQL server with 6 instances and your code does not product the instance name. It seem to work on default instance only.

    I like it.



  • This is odd as I've just ran it against a named instance and it works as expected. :(:unsure:

  • Are you executing this on a SQL server with more than one instance? I've tried on SQL server 64bit as I don't have any 32 bit servers.


  • Yes. On 32Bit though

  • Hi, this script is a great idea and does exactly what I needed to document some server settings before I apply a change to default data and log values.

    I have found a small bug in the script. If the DefaultData value is set but the DefaultLog is not set then the DefaultLog is displayed as the DefaultData value rather than the SQLDataRoot value. This is because the @path variable is no longer null going into the xp_instance_regread for the DefaultLog value. The xp does not find the value for DefaultLog as it is not set, and therefore does not alter the value in @path, but @path is not null as it contains the value from DefaultData set previously.

    To fix this I just added a SET @path = NULL before each call to xp_instance_regread

    Thanks again.

  • Exactly what I was looking for. I needed a path for automated tracing that the sql agent account had permissions to, and not dump everything in the root of C:\ like my predecessor in SQL 2000. It works on my multiple instance machine SQL2008.

    I added the following to get the default errorlog path

    SET @path = NULL

    exec @returncode = master.dbo.xp_instance_regread N'hkey_local_machine',N'software\microsoft\mssqlserver\CPE',N'ErrorDumpDir', @path output, 'no_output'

    Thanks a bunch!

    david hay

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

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