SQL Log Rescue Annoyances

Undo for SQL Server.

Moderator: eddie davis

SQL Log Rescue Annoyances

Postby mglenn » Fri Sep 15, 2006 11:13 pm

I recently started working with Log Rescue so some of this could be "user error", but:

1. During install you can choose to install extended stored procs on the default instance or not, but you can't specify a named instance during install (have to do that later).

2. Poor support for analyzing isolated log files. It might help to have more separation between analysis and recovery modes so users can analyze without having to meet the criteria necessary for successful recovery (such as access to the full backup, no missing logs, etc.).

3. Saving a project doesn't buy you much during the most labor intensive step--Choose Database Backups--because it ignores your saved choices and forces you to select files all over again when opening an existing project. (Not such a big deal unless you do frequent transaction log backups.)

Let me know if any of this is user error!
mglenn
 
Posts: 16
Joined: Wed Sep 13, 2006 2:36 pm

Postby Brian Donahue » Sat Sep 16, 2006 12:19 pm

Hi Mike,

Log Rescue may ask you to install the extended stored procedure, but it also very cleverly installs the XP automatically on the server when you choose to analyze a database on that server.

It's not designed specifically as an analysis/auditing tool, so it does have a shortcoming in that it can't simply dump a list of transactions from the log file. In order to fulfill the role of 'undo for SQL Server', it needs to know about the state of the schema and other things before it can proceed to geterate undo/redo scripts for the changes in the data that happen inside the log. This also results in some lengthy processing times before you can begin to work with the transactions in the log file.

Probably the project management could use some enhancement. I haven't got any suggestions for you in that area.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am

Postby mglenn » Sun Sep 17, 2006 1:56 am

Log Rescue is a nice utility really. Just wanted to suggest some minor tweaks.

1. True. Maybe something as simple as a parenthetical statement added to the dialog box "(The extended stored procedure can easily be created for named instances after intallation is complete.)" would help. This would save new customers from needlessly looking around for ways to specify a named instance during install, searching through the help file and possibly even contacting support only to discover a short time later that it's not a problem.

2. I understand. Expanding analysis functionality would obviously increase the price as well and no one would be happy about that. :wink:

3. Just retaining file selections in saved projects would be great.

Thanks for the quick response and taking time to discuss my feedback.
mglenn
 
Posts: 16
Joined: Wed Sep 13, 2006 2:36 pm


Return to SQL Log Rescue

Who is online

Users browsing this forum: No registered users and 0 guests