2008 64 bit msql server running slow until we restart the service

This problem arrises about once every 3 days.  We have on average about 125 users running an application that connects to 64 bit microsoft sql.  the server has 24 gig of memory and 16 gig is allocated to the application.  The developer says that 10 gig of mem to sql is more than enough.  the users run a remote desktop environment between 8 terminal servers.  all users slow down dramatically at about the same time.  There seems to be nothing wrong with the server.  no memory utitlization increase.  no spikes in cpu.  the select statements in real time monitor seem to snap along.  also some of the other applications running on the users session will seem to slow at the same time.   outlook for example.  when we restart the sql service all problems clear up.  users are fine for a few days.  until it arrises again.  we are scratching our heads.

8 terminal servers hosting 200 sessions.
all slow at the same time.  especially the app running on the sql server.
restart the service associated with that instance of sql server and everything speeds up.
please help
jamesmetcalf74Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Kyle AbrahamsConnect With a Mentor Senior .Net DeveloperCommented:
Locks are somewhat common.

I would double check the wait time
with this one:
select cmd,* from sys.sysprocesses
where blocked > 0

If you see that increasing you have a locking problem which the developer can isolate for you.

A good article about locking (grab a cup of coffee or something):
http://www.methodsandtools.com/archive/archive.php?id=83

Essentially locks block other users from using the same row/table while a user is working with it.  They are necessary, but if managed improperly, can wreak havoc.

Again, without knowing the full architecture of the application, it's impossible to know, but I know locking is one of the usual suspects.

You mentioned you have a developer . . . is it possible for him to troubleshoot?
0
 
Kyle AbrahamsSenior .Net DeveloperCommented:
any jobs running on the sql server?  Could be memory leaks in the application? (yes, even in .Net memory leaks still exist).

Could be a long running transaction and or databaselocks on the server itself.
0
 
jamesmetcalf74Author Commented:
no jobs that i know of
how can i find if their are memory leaks on the application.... the application runs slow across 200 users.... on 8 different machines. all at the same time.
we have decided the problem is some sortof connection with the sql database...
or the database itself but it looks fine under our eyes
we do not have a dba on staff
0
Easily Design & Build Your Next Website

Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store. Get started with your free trial today, and when ready, take 10% off your first purchase with offer code 'EXPERTS'.

 
jamesmetcalf74Author Commented:
how can i check for database locks or a transaction that is hanging around?
0
 
Kyle AbrahamsSenior .Net DeveloperCommented:
0
 
jamesmetcalf74Author Commented:
are locks common... i guess what im wondering is...
after i see the locks displayed.... how can i tell if that is bad or good.
or are all locks bad?
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.