Re: Killer scripts
From: JohnnyAppleseed (someone_at_microsoft.com)
Date: 02/09/05
- Next message: Aaron Weiker: "Re: Object reference not set to an instance of an object."
- Previous message: Joel H: "Re: 100% CPU Util on Simple Update Query"
- In reply to: DBA72: "Killer scripts"
- Next in thread: Joel Thornton: "Re: Killer scripts"
- Reply: Joel Thornton: "Re: Killer scripts"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 9 Feb 2005 13:35:18 -0500
The 'min server memory' and 'max server memory' configuration settings can
be used to restrict the amount of RAM available to SQL Server. Bumping this
down to 50 - 100mb or so would not only impact memory, but could affect disk
I/O and CPU due to disk swapping.
set transaction isolation level SERIALIZABLE or specifying the HOLDLOCK
option on a query will cuase a dataset to be exclusively locked.
The WAITFOR DELAY 'hh:mm:ss' statement can be used to pause processing in
the middle of a transaction, thus holding a lock on resources.
"DBA72" <DBA72@discussions.microsoft.com> wrote in message
news:35D5D71C-688D-4EBA-A3B5-0C9B8117F01C@microsoft.com...
> I am trying to understand how to monitor SQL Server for various
performance
> problems and would like to find some scripts to cause performance
problems.
> For example:
>
> A script causing high CPU usage
> A script causing high memory usage
> A script causing intensive IO
>
> Can anyone point me in the right direction or give me an idea of what kind
> of sql I could write to produce the above effects.
- Next message: Aaron Weiker: "Re: Object reference not set to an instance of an object."
- Previous message: Joel H: "Re: 100% CPU Util on Simple Update Query"
- In reply to: DBA72: "Killer scripts"
- Next in thread: Joel Thornton: "Re: Killer scripts"
- Reply: Joel Thornton: "Re: Killer scripts"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
