Hi Daniel,
What do you mean by maxed out. Is it "maxed out" on I/O, memory, CPU?
Run a trace in Performance Monitor using the following counters and once
you've identified the bottlenecks act accordingly, i.e. add more memory
or more/faster disks or RAID, fix application problems (if you're
getting blocking situations), remove other apps on the server etc. etc.
But before you take action you need inform yourself on what the
problem really is.
a. LogicalDisk (All Counters and All Instances)
b. Memory (All Counters)
c. Paging File (All Counters and All Instances)
d. PhysicalDisk (All Counters and All Instances)
e. Processor (All Counters and All Instances)
f. SQLServer:Access Methods (All Counters)
g. SQLServer:Buffer Manager (All Counters)
h. SQLServer:Buffer Node (All Counters and All Instances)
i. SQLServer:Buffer Partition (All Counters and All Instances)
j. SQLServer:Databases (All Counters and All Instances)
k. SQLServer:General Statistics (All Counters)
l. SQLServer:General Latches (All Counters)
m. SQLServer:General Locks (All Counters and All Instances)
n. SQLServer:General Memory Manager (All Counters)
o. SQLServer:General Plan Cache (All Counters and All Instances)
p. SQLServer:General Transactions (All Counters)
q. SQLServer:General Wait Statistics (All Counters and All Instances)
r. Thread (All Counters and All Instances)
Jonathan
[quoted text, click to view] Daniel wrote:
> Our high end SQL server cluster is maxed out, how else to expand? Will it
> help to move tables off of the cluster onto other clusters or will that just
> create processing bottleneck on the cluster running SQL server?
>
I'll have to agree. When the speakers sit around in the lounge at a big
conference we trade war stories about clients that have had literally tons
of hardware made unnecessary by some judicious tuning of the database or the
queries. In one case the customer (a BIG company) had not bothered to add
indexes to the tables. They were able to eliminate over half of their
servers. They saved a bunch of money on electricity and the salary of the
kid that designed the database.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com www.betav.com/blog/billva Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit
www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------
[quoted text, click to view] "JPD" <nospam@nospamplease.com> wrote in message
news:Ovf3gapzHHA.3536@TK2MSFTNGP06.phx.gbl...
> Hi Daniel,
>
> What do you mean by maxed out. Is it "maxed out" on I/O, memory, CPU? Run
> a trace in Performance Monitor using the following counters and once
> you've identified the bottlenecks act accordingly, i.e. add more memory or
> more/faster disks or RAID, fix application problems (if you're getting
> blocking situations), remove other apps on the server etc. etc. But before
> you take action you need inform yourself on what the problem really is.
>
>
> a. LogicalDisk (All Counters and All Instances)
> b. Memory (All Counters)
> c. Paging File (All Counters and All Instances)
> d. PhysicalDisk (All Counters and All Instances)
> e. Processor (All Counters and All Instances)
> f. SQLServer:Access Methods (All Counters)
> g. SQLServer:Buffer Manager (All Counters)
> h. SQLServer:Buffer Node (All Counters and All Instances)
> i. SQLServer:Buffer Partition (All Counters and All Instances)
> j. SQLServer:Databases (All Counters and All Instances)
> k. SQLServer:General Statistics (All Counters)
> l. SQLServer:General Latches (All Counters)
> m. SQLServer:General Locks (All Counters and All Instances)
> n. SQLServer:General Memory Manager (All Counters)
> o. SQLServer:General Plan Cache (All Counters and All Instances)
> p. SQLServer:General Transactions (All Counters)
> q. SQLServer:General Wait Statistics (All Counters and All Instances)
> r. Thread (All Counters and All Instances)
>
>
> Jonathan
>
>
> Daniel wrote:
>> Our high end SQL server cluster is maxed out, how else to expand? Will it
>> help to move tables off of the cluster onto other clusters or will that
>> just create processing bottleneck on the cluster running SQL server?
Don't see what you're looking for? Try a search.
