SQL Transaction Retreival Slow (Failing?)

[fcoa]

Posting this FYI for the good of the order (v9.0 U2).

On multiple occasions we've encountered seemingly never-ending spinning wheel when attempting to retrieve a SQL Transaction Log list with Explorer for SQL. In every case, this occurred when we had already successfully run a transaction LIST retrieval, then hit the backup button and tried retrieving a different list (same database). We waited 5 - 10 minutes before cancelling.

The solution each time was to fully cancel the Explorer for SQL process and then retry. On the retry, results returned in a less than a minute, as is more typical.


PS- The other potential cause I'd considered is a subsequent Transaction Log backup occurring while Explorer for SQL is running, but I haven't taken the time to validate that.

[foggy]

Eric, thanks for bringing our attention to this, we're currently trying to reproduce the described behavior. Will keep you posted.

[foggy]

Confirmed. Will be addressed in the future releases. Thanks again!

[fcoa]

Thanks for the prompt attention to the matter.

Out of curiosity, which was the actual cause? Attempting to run multiple transaction retrievals in a single Explorer for SQL session, or another transaction log backup occurring while Explorer for SQL is running.

[foggy]

The code causing this behavior is yet to be inspected. So far we've just reproduced the issue in the lab.

[corey.ike]

Can you tell Support what Bug Number this is so we can track the issue?

[nathanael.duke]

Also, is this in any way related to the execution priority of the agent? I have worked with one individual who was unable to consistently get log shipping to work on a busy SQL server until he used a third-party tool to forcibly raise the priority of the Log Shipping Agent's process. Unfortunately, the registry value "LowerAgentPriority" being set to 0 did not affect the execution priority of the Log Shipping agent process.

[foggy]

Do not have the bug ID yet. I don't think this is priority related.