Accessing Other Servers from SQL Log Rescue

To use SQL Log Rescue, an extended stored procedure called xp_LogRescue must be installed on the server for the database that you want to analyze.

The server must be running Microsoft® SQL Server™ 2000 on Windows 2000, Windows 2003, or Windows XP.

If your SQL Server instance user has access to the following procedures in the master database, SQL Log Rescue can install the extended stored procedure for you:

xp_regread
sp_oacreate, sp_oadestroy, sp_addextendedproc, sp_oamethod, sp_oasetproperty

Similarly, if your SQL Server instance user has access to the following procedures, SQL Log Rescue can uninstall the extended stored procedure:

xp_cmdshell
sp_dropextendedproc
dbcc (free)

You can use the menu commands provided on the Tools menu to install or uninstall the extended stored procedure in advance of analyzing a database. Alternatively, if you create or edit a project for which the server does not have the extended stored procedure installed, you will be prompted and SQL Log Rescue will install it.

If your SQL Server instance does not have these permissions, you must install and uninstall the extended stored procedure manually. In addition, you must install or uninstall the extended procedure manually if:

you are installing on a remote computer with SQL Server running in NT Fiber (lightweight pooling) mode
you are installing on a local computer with SQL Server running in NT Fiber mode and the current user does not have permissions to write to the MSSQL\Binn for the instance of SQL Server on which you want to install or uninstall the file

If you are unable to install the extended procedure on the server, for example if it is a customer's server, back up the database and the transaction log on the remote server, then restore and recover the database on a local server on which the extended procedure can be installed. Note that if you need to repeat this procedure do not overwrite the local copy; you must drop or rename the original copy of the database on the local server, or restore the new copy to a different name.

Using SQL Log Rescue to install or uninstall

To install the extended stored procedure:

On the Tools menu, click Install Extended Stored Procedure.
In the Server list, click the server for the database that you want to view.
SQL Log Rescue lists only those servers currently running on the local area network (LAN).

If you experience problems selecting a server that is not running on the LAN, for example if you are accessing the server via an internet connection, you may need to use SQL Client Connection Manager to create an alias to the server using TCP/IP. You can then type the alias name in the Server box to connect to the remote server.

To refresh the Server list, scroll to the top of the list and click Refresh.
Select the authentication method, and for SQL Server authentication enter the User name and Password.
Click Install.

To uninstall the extended stored procedure, on the Tools menu, click Uninstall Extended Stored Procedure, select the server as described above, and then click Uninstall.

To install or uninstall manually

To install the extended stored procedure on a database server:

Copy the file xp_LogRescue.dll from your installation folder to the folder MSSQL\Binn for the instance of SQL Server on which you want to install the file.
By default, your installation folder is C:\Program Files\Red Gate\SQL Log Rescue, and MSSQL\Binn is located in C:\Program Files\Microsoft SQL Server.
Run the following command:
exec sp_addextendproc 'xp_LogRescue', 'path\xp_LogRescue.dll'

If you need to replace the extended stored procedure manually, for example to upgrade your installation:

Drop the existing version using the command exec sp_dropextendedproc.
Free the dll using the command dbcc xp_LogRescue (free)
Copy the new extended procedure as described above.