SqlServer weekend job blocked by a user left open screen

[Chaim Fried]

Hello!
We have a maintenance job on MSSQL server scheduled for the weekend.
some times we arrive at the beginning of a week and see that a user left
his screen open on a SQL record and the job is still waiting blocked by
that user. Please give me an idea how to overcome this.
Thanks in advance
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Louis]

Kill that user's process(es).

"Chaim Fried" <mo****@pwd.gov.il> wrote in message
news:3f***********************@news.frii.net...

Hello!
We have a maintenance job on MSSQL server scheduled for the weekend.
some times we arrive at the beginning of a week and see that a user left
his screen open on a SQL record and the job is still waiting blocked by
that user. Please give me an idea how to overcome this.
Thanks in advance
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Dan Guzman]

If you are running SQL 2000, you can terminate all connections to the
database with:

ALTER DATABASE MyDatabase
SET SINGLE_USER WITH ROLLBACK IMMEDIATE

and resume normal operation with:

ALTER DATABASE MyDatabase
SET MULTI_USER WITH ROLLBACK IMMEDIATE
--
Hope this helps.

Dan Guzman
SQL Server MVP

-----------------------
SQL FAQ links (courtesy Neil Pike):

http://www.ntfaq.com/Articles/Index....partmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
-----------------------

"Chaim Fried" <mo****@pwd.gov.il> wrote in message
news:3f***********************@news.frii.net...

Hello!
We have a maintenance job on MSSQL server scheduled for the weekend.
some times we arrive at the beginning of a week and see that a user left his screen open on a SQL record and the job is still waiting blocked by that user. Please give me an idea how to overcome this.
Thanks in advance
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Greg D. Moore \(Strider\)]

"Dan Guzman" <da*******@nospam-earthlink.net> wrote in message
news:tw*****************@newsread1.news.atl.earthl ink.net...

If you are running SQL 2000, you can terminate all connections to the
database with:

ALTER DATABASE MyDatabase
SET SINGLE_USER WITH ROLLBACK IMMEDIATE

and resume normal operation with:

ALTER DATABASE MyDatabase
SET MULTI_USER WITH ROLLBACK IMMEDIATE
--
Hope this helps.
I'm going to jump in and say that while Dan's solution certainly works, I
think his reply and the other one missed what I think is the fundamental
problem: The application.

It appears that the application is creating some sort of lock on the DB that
lives as long as the screen is open.

This is inherently non-scalable.

I'd look much into HOW the application was able to hold a lock on the DB
like that and focus on that for the long-term solution.


Dan Guzman
SQL Server MVP

-----------------------
SQL FAQ links (courtesy Neil Pike):

http://www.ntfaq.com/Articles/Index....partmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
-----------------------

"Chaim Fried" <mo****@pwd.gov.il> wrote in message
news:3f***********************@news.frii.net...

Hello!
We have a maintenance job on MSSQL server scheduled for the weekend.
some times we arrive at the beginning of a week and see that a user

left

his screen open on a SQL record and the job is still waiting blocked

by

that user. Please give me an idea how to overcome this.
Thanks in advance
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Chaim Fried]

Thanks all for answers

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!