|
|
Posted by Erland Sommarskog on 01/13/08 10:44
Ed Murphy (emurphy42@socal.rr.com) writes:
> A couple users at one client are complaining of early morning
> slowness in their OLTP system. The first thing that came to
> mind is that the nightly backup might be using close to 100% of
> the memory cache. (IIRC, they have 16 GB of RAM, 12 of which
> is reserved for MSSQL, while the DB is roughly 30 GB.)
>
> Is there a way to limit how much memory cache the backup uses? (It
> only takes about 15 minutes now, so we can afford to slow it down
> in order to speed user operations up.)
I would first analyse whether the problem is really due to that cache having
been flushed.
If that really is the case, I would investigate what might be flushing the
cache. I don't know for sure, but I don't think it's the backup. They could
have some nightly batch jobs that slurps memory. Or for that matter, they
may be defragmenting tables every night. (And who knows: may be the
reindexing has started to spill into early morning, and that's why the
users find the system slow.)
--
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]
|