Killer scripts

From: DBA72 (DBA72_at_discussions.microsoft.com)
Date: 02/09/05 

Date: Wed, 9 Feb 2005 09:31:08 -0800

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.

Relevant Pages

  • mdadm warning: superfluous parity checks ahead
    ... a script that checks the parity information of redundant ... often, but it can cause performance problems, and it is extra strain ... Please do not send copies of list mail to me; ...
    (Debian-User)
  • Performance problem?
    ... I'm having performance problems in the following scenario: ... the large amount of data). ... I then run a script with 3 delete and about 25 ... table and recreate this process. ...
    (microsoft.public.sqlserver.server)
  • Re: gawk: invalid argument
    ... > The script is more than 600 lines long. ... > Apparently it is the length of the script causing gawk to bark ... > This workaround parses the first half of the infile, generates output, ...
    (comp.unix.shell)