I was really interested in your product (had some problems getting it run on SQL 2k, but your forum support tip helped)..sadly SQL 2k is not what i need.

I have contacted Lumigent and they indicated they will have SQL2005 support for Log Explorer in 30 days. I'm not sure I understand the implication on this page: http://redgate.com/products/sql_log_res ... _plans.htm that Microsoft is disallowing log reading tool vendors from supporting SQL2005 when Lumigent appears to be about ready to release a version that does just this, as clearly this isn't the case. At least according to Lumigent.

As leaders on third party SQL tool market and based on my experience you really do make top notch tools - why can't you catch up with technology, while others do?

msekez wrote:I'm not sure I understand the implication on this page: http://redgate.com/products/sql_log_res ... _plans.htm that Microsoft is disallowing log reading tool vendors from supporting SQL2005 when Lumigent appears to be about ready to release a version that does just this, as clearly this isn't the case. At least according to Lumigent.

Guys, any word on this? We look for an appropriate product being able to rescue SQL 2005 db's. I was disappointed when saw that you don't have any plan for that:

Chris Auckland wrote:There are no current plans for SQL Log Rescue to support SQL 2005 transaction logs. It may be something that is considered in the future, buy currently it is not on the horizon.

I know how one can be left flapping in the breeze by MSFT over licensing issues, so I'd simply like to know this - "Is Red Gate actually trying to get closure on this so that SQL Server 2K5 can be supported?"

I'd like to know because if this is just going to lay here forever, then I need to get about finding a suitable replacement. Whereas if this is being actively worked, then I could maybe sit and wait it out.

It is the not knowing about the current status that is giving me heartburn.

I'm in the process of trying to get an official statement about this. This is why this topic has been so silent on our end.

What Chris had said is the truth: Microsoft are imposing some restrictions on the log file documentation, but this isn't meant to signify that this is the final word. We're still trying to get Microsoft to see things our way.

I think we've learned that it's technically challenging enough to try to analyze a live log file, without the additional problem of making assumptions about the file format. This combination often results in unstable software or software that doesn't live up to its full potential.

I do appreciate what you're saying though. It would be a challenge worthy of a great programmer to hack Microsoft's file format by brute force!

Correct me if I'm wrong, but I don't see a way in Quest Log Reader to recover the data from a dropped table. Log Rescue can recreate the table and recover the data. I think their program is mainly just a log analyzer more than a data recovery tool in my humble opinion.

Correct me if I'm wrong, but I don't see a way in Quest Log Reader to recover the data from a dropped table. Log Rescue can recreate the table and recover the data. I think their program is mainly just a log analyzer more than a data recovery tool in my humble opinion.

Hi Brian,
Out of frustration of purchasing your product and getting the subscription. How do you have any room to talk about this any more at Red Gate?

You have let customers down by stopping development of this product. It is now useless. One big issue. "At Least" this one ca read SQ 2005.

Please don't try and sugar cote this and compare your product to this. It is nice that Log rescue can recover data but only in SQL 2000. Humm it is 2007 and SQL 2005 has been out for almost 2 years now.

Thanks arila for posting the link. I will start to look at there products. Maybe support from this community can have them add development to make a product that works in SQL 2005.

Sorry, I was not trying to sugar coat the issue. I was pointing out that these two products are not exactly the same.

Also to clarify, development has not stopped on Log Rescue -- it's just on hold until the licensing issue is straightened out. Admittedly this isn't a top priority for Red Gate, but Log Rescue shouldn't be considered orphan-ware just yet.

As an avid user of the Red-Gate products, I'm curious to how other companies can have tools released for SQL 2005, but you all are blocked by Microsoft due to a licensing issue? Not attacking, but simply curious what the other companies are doing to work around this issue, or are they running into the same roadblocks?