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
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
ASKER
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
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
ASKER
how can i check for database locks or a transaction that is hanging around?
Google is a wonderful thing ;-)
http://stackoverflow.com/questions/694581/how-to-check-which-locks-are-held-on-a-table
http://stackoverflow.com/questions/694581/how-to-check-which-locks-are-held-on-a-table
ASKER
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?
after i see the locks displayed.... how can i tell if that is bad or good.
or are all locks bad?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Could be a long running transaction and or databaselocks on the server itself.