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 |
|
CanadaDBA
583 Posts |
 Posted - 2004-09-27 : 08:30:35
|
| Starting 7am to 8pm, our server is busy with daily works. 8pm to 12:30am it is doing integrity checks and optimization as well as backups. A process had locked a table and therefore, we had problem the day after. It seemed that a user had left his/her computer without closing the application or even may had turned off the computer. What can I do as a DBA? Should I have a script that check the processes early in the morning for example 3:00am and kills all processes? What is a good decision?Canada DBA |
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2004-09-27 : 10:45:14
|
| Perhaps you should tell your programmers not to leave the connections open once they have retrieved the data they need...Other than that, you could schedule a job to kill all user processes, there are some examples on this site I think... |
 |
|
|
CanadaDBA
583 Posts |
Posted - 2004-09-28 : 11:53:43
|
| Is it possible to set a time limit on idle connections? For example if a connection was idel for 2 hours, then disconnect that connection and release the reources. How harmfull it would be?Canada DBA |
|
|
|
|
|
|
Open left process