Best Practices to Diagnose Windows 2003 Server Network Performance

Dear Experts,

I need to run some performance tests on our server to determine how we can improve the server's performance.

The Server is a Windows 2003 Server, running Acomba (acounting) software.

The way our company connects to this server is by mapping a network drive to that server and running the Acomba.exe application directly from the server. The amount of users on that machine has risen from 6 to about 20 users.

After speaking with the Acomba Company, they say it's the correct configuration so I cannot modify the way Acomba works, it must remain the same.

The problem is that Acomba (and an ASPX intranet site on the same server) respond very slowly to "certain" requests. (particularly when adding or editing records).

What is the Best Practice for me to determine where the bottleneck is on the Server so I can find appropriate solutions?

i'm obviously going to look into Hardware upgrades but I first need to determine how many resources are needed to provide a performing service (for Acomba and the ASPX intranet site).
LVL 1
DraceAsked:
Who is Participating?
 
DraceAuthor Commented:

Thanks for the links, It's a good start but where would I go to narrow down the problem?

I already knew about Performance Monitor and I am aware of the memory issue, I'm trying to determine which program or user is hogging most of the resources.. or find stuff that needs to be cleaned up which will speed up the process.

0
 
shalabhsharmaCommented:
You can check the memory usage of each process

You can also use debug diagnostic
http://support.microsoft.com/kb/919790

For MSSQL http://www.zabbix.com/forum/showthread.php?t=1958&highlight=microsoft+sql&page=3
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.