May 16, 2009 at 2:49 am
nilmov (5/15/2009)
i would suggest lets run a command likewhile(1=1)
select * from master.dbo.sysprocesses
wait for delay 00:00:15
Or run profiler that will capture everything that runs on the system while the trace is active, along with username, app name, host name, IP and the full command
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 16, 2009 at 11:28 am
I'm the original poster of this problem from a year ago. All the suggestions about trapping what is happening at the time are good. Since you know when it happens, scheduling sp_who2 and sending the output to a file might tell you what you need to know.
Also check that maintenance plan job you have running at midnight to make sure it has no additional steps other than the integrity check. Look for anything that runs Transact SQL or a stored procedure. And - try to find out if the application performs any sort of maintenance at midnight.
You could change your full backup to run at 12:05 (right after the event, whatever it is) until you figure it out.
Viewing 2 posts - 31 through 31 (of 31 total)
You must be logged in to reply to this topic. Login to reply