So....
SELECT distinct (on several large tables) will load test my SQL Server
for RAM usage
AND
UPDATE OR INSERT on several large tables will load test the CPU...or do
I need to make that a cursor so it runs an UPDATE and then another
one...and then another one....
?????

-K

-----Original Message-----
From: Mark.[Email Address Removed] Friday, February 22, 2002 3:40 AM
To: Sexton, Kevin
Subject: RE: RAM usage


Aggregate operations on large data sets, SELECT DISTINCT, ORDER BY
clauses
on columns not in clustered index, and a few others...

SQL Server is usually I/O bound though.

-----Original Message-----
From: Sexton, Kevin [mailto:kevin.[Email Address Removed] 21 February 2002 21:10
To: [Email Address Removed] RAM usage


What type of activities are RAM intensive for SQLSERVER?????

What is CPU intensive? (writing to disk, row level updates, etc?)

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed] message and any attachment are confidential and may be privileged
or otherwise protected from disclosure. If you are not the intended
recipient, please telephone or email the sender and delete this message
and any attachment from your system. If you are not the intended
recipient you must not copy this message or attachment or disclose the
contents to any other person.

For further information about Clifford Chance please see our website at
http://www.cliffordchance.com or refer to any Clifford Chance office.
MS Sql Server LazyDBA home page