SQL Log Rescue - Current Version & Memory Problems
owenh
Posts: 25
I have recently upgraded my installations of SQLBAckup and SQLLogRescue on my Production Servers. SQLBackup seems to be running well, but I am experiencing problems with the SQL Log Rescue applicaiton.
First, the version from the About box for SQLLogRescue is 1.0.0.1044.
The database I am attempting to test with gives the following error:
Unable to connect to databse [(local)[Amx_QA] to retrieve backup files. Ensure you have access to the database.
Exception of type System.OutOfMemoryException was thrown.
I get the same error whether using an admin account or the "sa" account.
I ran this query :
SELECT distinct physical_device_name FROM msdb..backupmediafamily
WHERE media_set_id IN (SELECT media_set_id FROM msdb..backupset
WHERE database_name = N'Amx_QA' AND type LIKE '[LDI]'
AND database_creation_date IN (SELECT MAX(database_creation_date) FROM msdb..backupset WHERE database_name = N'Amx_QA')
) AND device_type IN (2,7,102)
And it returns 4287 rows.
Any suggestions?
Thanks.
First, the version from the About box for SQLLogRescue is 1.0.0.1044.
The database I am attempting to test with gives the following error:
Unable to connect to databse [(local)[Amx_QA] to retrieve backup files. Ensure you have access to the database.
Exception of type System.OutOfMemoryException was thrown.
I get the same error whether using an admin account or the "sa" account.
I ran this query :
SELECT distinct physical_device_name FROM msdb..backupmediafamily
WHERE media_set_id IN (SELECT media_set_id FROM msdb..backupset
WHERE database_name = N'Amx_QA' AND type LIKE '[LDI]'
AND database_creation_date IN (SELECT MAX(database_creation_date) FROM msdb..backupset WHERE database_name = N'Amx_QA')
) AND device_type IN (2,7,102)
And it returns 4287 rows.
Any suggestions?
Thanks.
This discussion has been closed.
Comments
Can you please try a beta of version 1.1 and see if that helps? There is a memory issue with 1.0 when your backup history is mega-huge. V1.1 will only retrieve a limited subset of the backup history and should fix the problem. You can download the fix from ftp://ftp.red-gate.com/SQLLogRescueSetup110Build204.zip