SQL 2005 on new server performance issues

Question

SQL 2005 on new server performance issues

Eric Venden

SSC Rookie

Points: 29
More actions
April 11, 2007 at 9:37 am

#173408

We are having some issues with performance on a new (less than 3 months) server with 4GB of RAM.
It is a Windows Server 2003 box w/SQL 2005 on it. It is also the domain controller BUT there are not that many users "hitting" it (maybe 35).
We have a third party app (Police Records Management) running that hits the SQL Server..and we have had some performance problems as of late with SLOW performance.
Could someone point me to which "counters" I should consider checking and for how long? I have run perfmon and profiler, but with perfmon there are MANY sql objects to look at....I'm trying to narrow it down...
Additionally, which "locks" should I be concerned about?
Thanks for any assistance.
Eric V

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 1

Part of the problem could be that you have SQL Server on domain controller. That alone could take up quite a bit of system resources even if there are only 35 users hitting the server. I would look at seeing if it is possible to get a seperate server to host SQL Server 2005. If not, you may want to fix the amount of memory that SQL Server uses to ensure it has enough memory to work with.

Do a search of this site, I am pretty sure I have seen a couple of articules that discuss this issue.

Grant Fritchey SSC Guru Points: 398882 More actions · Answer 2

This is one well documented approach for performance tuning:

http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/performance_tuning_waits_queues.mspx

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

EdVassie SSC Guru Points: 60472 More actions · Answer 3

I would only put SQL on a domain controller if it was the only machine in the domain. It seems you have at least 35 other machines in the domain... Having SQL on the domain controller is bad for performance, and horrible for security.

Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara