Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jar21
51 Posts |
 Posted - 2008-09-11 : 13:15:57
|
| for some reason and application that both the front end and back end office use to interface with our sql database sometimes begins freezing up and suspending sessions with users unable to update any changes, the company that set this up has recommended we restart the sqlserver.exe service on the server, this temporarily fixes the situation. Can this be done while people are logged into the application that connects to the database? Is there an alternative, is this normal?just a few questions, I believe that maybe the server that sql 2005 is on cant hand all of the requests. We are also running roaming profiles (I dont know why but its not my call to make) which may be effecting the server because the profiles are located on that server as well...thanks for any advice given!Enjoy Life This Is Not A Rehearsal. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-09-11 : 13:43:01
|
| Restarting that service is not a solution. It causes downtime for all of the databases on that SQL Server instance. The solution is to figure out where the issue is by running SQL Profiler, Performance Monitor, and perahps the Performance Dashboard reports. Get a DBA involved to diagnose what the issue and you won't need to do this unnecessary step of downtime.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
 |
|
|
jar21
51 Posts |
Posted - 2008-09-11 : 15:37:51
|
| okay thanks, I'll check em outEnjoy Life This Is Not A Rehearsal. |
|
|
|
|
|
|
Sqlserver.exe