Red Gate forums :: View topic - Dead in the water: SQL Log Rescue Freeze
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Log Rescue
SQL Log Rescue forum

Dead in the water: SQL Log Rescue Freeze

Search in SQL Log Rescue forum
Post new topic   This topic is locked: you cannot edit posts or make replies.
Jump to:  
Author Message
binggeli



Joined: 12 Jan 2006
Posts: 2

PostPosted: Thu Jan 12, 2006 5:30 pm    Post subject: Dead in the water: SQL Log Rescue Freeze Reply with quote

For the second day in a row, I have single-handedly brought the database server down, using SQL Log Rescue.

I am pretty sure that I must have done something wrong, but I cannot figure out for the life of me what's going on.

Yes, I am new to SQL Log Rescue, but I have used other, similar tools in the past and never had any issues with crashing database servers.

DAY 1:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Tried to run SQL Log Rescue remotely (from my office computer to the database server in the remote data center). Since I didn't want the extended SP on my local instance of SQL Server (never use any databases on my machine), I let SQL Log Rescue install the extended SP on the remote server.

Then SQL Log Rescue came up with a screen full of potential backups, but they all had the "red x" icon and said they were unavailable. Unchecked the "Use the following backups" (or similar) check box and clicked Next.

Then I got the "Analyzing Transaction Log" (or something like that) window with a progress bar, and SQL Log Rescue just sat there. And sat there. And nothing happened for minutes. No progress in the progress bar either.

So I shut down SQL Log Rescue (clicked Cancel) and within seconds, our production database went down.

I had to call the data center and somebody had to walk over to our server and cold-reboot it because it was frozen and didn't accept any commands from anyone anymore.


DAY 2:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Because red-gate has this awesome advertising slogan, "Recover SQL Server data without any downtime" I thought I'd give it another try.

This time, however, I installed SQL Log Rescue directly on the database server, let it do its thing with the extended SP (which I thought was odd since that got installed yesterday already . . . ?) and wanted to find out when some specific data were entered into a client account.

Same thing all over again. Got as far as the window with the progress bar but nothing happened whatsoever. No "busy" cursor, no little thingies moving along in the progress bar, nothing at all.

So I thought I'd make use of the Cancel button, saw a message that stated something about SQL Log Rescue wanting to cancel the operation and waited. And waited. And waited.

Within a few minutes, our production database went down again.

Unfortunately, I couldn't get a hold of anyone at the data center at that time (they were all out working on different servers for other clients at just that time), and I ended up with a 40-minute downtime.



So, has anyone else had any similar experiences?
If so, how can I fix this?


We're running SQL Server 2000 on a Windows 2000 Server with 3GB of RAM.


Can anyone help me to get SQL Log Rescue running, or should I ask for my money back? Just wondering.



Thanks,

Dee
Back to top
View user's profile Send private message
Brian Donahue



Joined: 23 Aug 2004
Posts: 6643

PostPosted: Fri Jan 13, 2006 12:00 pm    Post subject: Reply with quote

Can you please write to support@red-gate.com for a beta version of Log Rescue? The problem here is most likely that the process is spawning more threads than your OS can safely handle. We have introduced some throttling to prevent this but the fix is only available internally at this time.
Back to top
View user's profile Send private message
binggeli



Joined: 12 Jan 2006
Posts: 2

PostPosted: Fri Jan 13, 2006 3:10 pm    Post subject: Thank you Brian Reply with quote

Greatly appreciate your reply.

Did what you suggested. We'll have to see how that turns out.



Thank you,
Dee
Back to top
View user's profile Send private message
dejansen



Joined: 26 Jan 2006
Posts: 1

PostPosted: Thu Jan 26, 2006 7:18 pm    Post subject: Have this issue been addressed? Reply with quote

I have purchased SQL Backup and since SQL Log Rescue came with it, I'd like to give SQL Log Rescue a spin to see how it compares to Lumigent's Log Explorer. It would be great to have some assurance that it will not bring down my SQL servers. Thank you.
Back to top
View user's profile Send private message
Brian Donahue



Joined: 23 Aug 2004
Posts: 6643

PostPosted: Fri Jan 27, 2006 11:59 am    Post subject: Reply with quote

SQL Log Rescue performs minimal actions on the server. It installs an extended stored procedure on the server and that reads the log file to return the relevant bits of data. The rest of the work is done on the client.

The only way that I can see Log Rescue killing a server (if the client is another computer; a workstation on the same network) is if the SQL Server is low on memory or badly unstable. For instance a SQL Server with lots of extended stored procedure code and low memory could be the culprit.
Back to top
View user's profile Send private message
Display posts from previous:   
This topic is locked: you cannot edit posts or make replies. All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group