So I was trying out your tool and now our main 24x7 customer-facing production server is totally unavailable, out of memory and off the net. Cool!
Similar to problems reported on this forum, I have just seen:
- LR mysteriously wants to install the ExtendedProcedure when it's already been installed
- During Analysis (70Gb .mdf and 10Gb of .trn log files - all local to LR) LR hangs with System.Out of Memory Exception
Shortly thereafter, my whole database server (and both DB instances, one of which I did not touch with LR) hangs. It runs Enterprise 2000 SP3 with 4Gb RAM.
The last Event messages that made it to external monitoring talk about unpaged memory pool being empty and the network interface dying. Now the server is not responding at all, I'm off to the hosting centre to give it a kick up the backside.
Using LogRecovery 18.104.22.168.
Having read this forum, I will try the 1.1 beta, but I'm distinctly nervous. It's obviously very embarassing to very publicly crash a production server while testing a new tool. Doesn't really encourage my company to want to buy the products! I would suggest you distribute the beta as well as the 1.0 version and give a strong disclaimer to use the beta on large history sets / recovery sets.
In general I'm still believing in your products and I like the honest atmosphere of this support forum.