|
|
Posted by Erland Sommarskog on 01/14/08 22:23
Ed Murphy (emurphy42@socal.rr.com) writes:
> Erland Sommarskog wrote:
>> I would first analyse whether the problem is really due to that cache
>> having been flushed.
>
> How would I go about that? Profiler trace, looking for lots of cache
> misses during the early morning?
There is of course, the traditional route of running a trace to catch
slow procedures and monitor blocking.
That may reveal something that leads you to diffierent track altogether.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|