Hello,
i have a quite general questions:
We have some performance issues with our SQL 2005 Server and are looking for possible causes.
Here some details about our Test Setup ( we've got 3 systems ):
- Windows 2003 R2 x86
- SQL 2005 SP2 x86
- 2 - 4 GB Memory
- 4 GB SWAP ( own Disk )
- Logs, Database and System files are all on seperate Disks located on a high speed SAN.
- approx. 30 Instances per Server
- approx. 50 %- 60% overall CPU Usage
- we have 1 ( single cpu ), 1 ( dual cpu ), and 1 ( quad cpu ) systems all with the same setup as stated above
- The Databases are application specific databases like WSUS and so on ( so we can't optimize there structure or indexes )
What are we looking for ?
Just some Hints, Tipps and maybe important SQL Settings which could help us to get hold of our Performance Problems.
Maybe there are some known caveeats and frauds which someone could
unwillingly do to reduce the performance.
Questions which YOU could answer:
"Is it wise to restrict an Instance to a specific amount of Memory ? e.g. 256MB ?"
"Isn't the Default Setting of 1MB per SQL Query too high ?"
"When i Setup a Windows 2003 Server with one CPU and add a second CPU later,
does the System HAL recognize this change correctly and make use of the new SMP features ?"
"What is most important for an SQL 2005 Server, having more Memory or more CPU's ?"
with best regards,
FireArmz
Start Free Trial
