February 12, 2015 at 2:07 pm
I have the default trace on a SQL Server 2008R2 instance enabled and found today that there is a gap of nearly 4 minutes in the trace during a time of the day when there most certainly is not going to be a 4 minute window of nothing.
What if anything could cause the default trace to have a gap like this? The SQL Server Instance (against my preferences) is hosted on VMware however it has its on HOST and so its resources are not being shared with any other server. The data & log files reside on different parts of the SANS. Our IT & Network admins are looking into the issue on their end but when I looked and found a near 4 minute gap in the default trace it hit me that this could be something above/outside of SQL Server.
Thoughts?
Kindest Regards,
Just say No to Facebook!February 25, 2015 at 2:07 pm
SO is this the kind of question that is so blaringly obvious that no one wants to answer or is it something unheard of? Just trying to figure out why there's not been a single thought on this when typically a post gets at least 1 if not several comments.
Thanks
Kindest Regards,
Just say No to Facebook!Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply