April 15, 2009 at 3:24 am
Hello all,
Just a quick question.
I have log shipping between a live and secondary server, and recently the log shipping has been failing at the same time every night (4.35am).
Something is kicking off around this time and querying the read only DB and locking it out (There should be nothing querying this DB) causing a log shipping failure.
It is a farily small DB so it is no problem to resynchronise the shipping jobs, but I'd rather find the cause and save having to do it every morning! 🙂
Is there a quick way to check what was locking out the DB at the time?
There is nothing in the SQL logs or the failure messages indicating a source.
Many thanks in advance for any responses.
April 15, 2009 at 5:28 am
The easiest way would be scheuling a profiler trace.
Since you can't schedule it directly from profiler you have to take a few extra steps.
1. Define your trace in profiler and run it for a few seconds.
2. Under the file menu select Script trace to create a sql file
3. Schedule a job to execute the script around the time you want to trace.
You can find a more extensive description here:
http://blogs.msdn.com/john_daskalakis/archive/2008/11/20/9128270.aspx
[font="Verdana"]Markus Bohse[/font]
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply