Connections & Single-User

Hello all,
As an sql novice I have created some Maintenance Plans which seemed to work
ok except for integrity checks. As I can read from the logs they could'n be
executed because the db had to be in Single-User. Ok got that.
But the problem is that other servers are running some foreground &
background programs that connect to the sql svr. When I closed the
connections on our sql, the other server keeps connecting back resulting in
the fact I couldn't close the connections. This weekend when I rebooted the
other servers they lost connection to sql resulting in 0 connections to the
db.
How can this be done then, if remote servers keep connecting ? Is there a
safe way to get my db's in single user ?
I presume my test by closing the active connections to the sql via Ent. Mgr
was also not a good thing to do?
Rgds,
T.
The way to handle it is to remove the check for the option
to repair errors on your integrity checks in the maintenance
plan. You don't really want automatic repairs happening if
your dbcc checkdbs fail. You would want to intervene
yourself, determine what caused the consistency error, fix
the underlying problem and then take whatever course of
action based on what the underlying problem is.
-Sue
On Mon, 20 Sep 2004 19:21:26 GMT, "TieTo" <nobody@.home.net>
wrote:

>Hello all,
>As an sql novice I have created some Maintenance Plans which seemed to work
>ok except for integrity checks. As I can read from the logs they could'n be
>executed because the db had to be in Single-User. Ok got that.
>But the problem is that other servers are running some foreground &
>background programs that connect to the sql svr. When I closed the
>connections on our sql, the other server keeps connecting back resulting in
>the fact I couldn't close the connections. This weekend when I rebooted the
>other servers they lost connection to sql resulting in 0 connections to the
>db.
>How can this be done then, if remote servers keep connecting ? Is there a
>safe way to get my db's in single user ?
>I presume my test by closing the active connections to the sql via Ent. Mgr
>was also not a good thing to do?
>Rgds,
>T.
>
>
|||"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:4h5vk0l1mvrer6h775b6dgb2slkg5441r0@.4ax.com...
> The way to handle it is to remove the check for the option
> to repair errors on your integrity checks in the maintenance
> plan. You don't really want automatic repairs happening if
> your dbcc checkdbs fail. You would want to intervene
> yourself, determine what caused the consistency error, fix
> the underlying problem and then take whatever course of
> action based on what the underlying problem is.
> -Sue
>
Ok Sue, I will do so. Thank you for your help!!
Rgds,
T.