Kill Session statement does not work

I logged in through query anayzer as system admin and then logged in a second session from a different user ID. From the sa window I issued "sp_who" and found the session id of 55 for the second logged in session. I then issued "KILL 55". When I reissued
"sp_who" it showed the session id was gone, but when I opened the user query analyzer window, I was still allowed to issue SELECT statements. Shouldnt the user session window close or leave some type of message to show that the session was logged out and
the window is no longer active?
> Shouldnt the user session window close or leave some type of message
> to show that the session was logged out and the window is no longer
active?
The actual behavior is that Query Analyzer will try to reestablish the
connection when you try to execute a query against a closed connection. You
can see this with a Profiler trace. Whether or not QA should notify the
user when this occurs is debatable.
Hope this helps.
Dan Guzman
SQL Server MVP
"Jack Wachtler" <jack_wachtler@.comcast.net> wrote in message
news:AA7FD110-6FD0-44D5-A011-EE320063ABC8@.microsoft.com...
> I logged in through query anayzer as system admin and then logged in a
second session from a different user ID. From the sa window I issued
"sp_who" and found the session id of 55 for the second logged in session. I
then issued "KILL 55". When I reissued "sp_who" it showed the session id was
gone, but when I opened the user query analyzer window, I was still allowed
to issue SELECT statements. Shouldnt the user session window close or leave
some type of message to show that the session was logged out and the window
is no longer active?

Kill Session statement does not work

I logged in through query anayzer as system admin and then logged in a secon
d session from a different user ID. From the sa window I issued "sp_who" and
found the session id of 55 for the second logged in session. I then issued
"KILL 55". When I reissued
"sp_who" it showed the session id was gone, but when I opened the user query
analyzer window, I was still allowed to issue SELECT statements. Shouldnt t
he user session window close or leave some type of message to show that the
session was logged out and
the window is no longer active?Hi,
Query analyzer will establish back the connection to SQL server on issuing
any SQL / DML statements.
Thanks
Hari
MCDBA
"Jack Wachtler" <jack_wachtler@.comcast.net> wrote in message
news:AA7FD110-6FD0-44D5-A011-EE320063ABC8@.microsoft.com...
> I logged in through query anayzer as system admin and then logged in a
second session from a different user ID. From the sa window I issued
"sp_who" and found the session id of 55 for the second logged in session. I
then issued "KILL 55". When I reissued "sp_who" it showed the session id was
gone, but when I opened the user query analyzer window, I was still allowed
to issue SELECT statements. Shouldnt the user session window close or leave
some type of message to show that the session was logged out and the window
is no longer active?|||> Shouldnt the user session window close or leave some type of message
> to show that the session was logged out and the window is no longer
active?
The actual behavior is that Query Analyzer will try to reestablish the
connection when you try to execute a query against a closed connection. You
can see this with a Profiler trace. Whether or not QA should notify the
user when this occurs is debatable.
Hope this helps.
Dan Guzman
SQL Server MVP
"Jack Wachtler" <jack_wachtler@.comcast.net> wrote in message
news:AA7FD110-6FD0-44D5-A011-EE320063ABC8@.microsoft.com...
> I logged in through query anayzer as system admin and then logged in a
second session from a different user ID. From the sa window I issued
"sp_who" and found the session id of 55 for the second logged in session. I
then issued "KILL 55". When I reissued "sp_who" it showed the session id was
gone, but when I opened the user query analyzer window, I was still allowed
to issue SELECT statements. Shouldnt the user session window close or leave
some type of message to show that the session was logged out and the window
is no longer active?

Keep getting update

I keep getting a critical update for SQL Server 2000 Desktop Engine(Windows)
in Window Server 2003(KB829358), I install the update and it keeps
redownloading the update. Can anyone help me with this issueHi Lloyd
Check the version you are currently on and see if it is higher than
8.00.0884, if it is then you may not need the update and might be able to
remove it by using the custom install and checking the don't show this update
option.
If you want to install it manual it can be download from
http://www.microsoft.com/downloads/details.aspx?familyid=814c230b-5c53-453f-810a-b9505acf1392&displaylang=en.
Also make sure that your account has enough permissions to install the
update and update the registry.
John
"Lloyd Pratt" wrote:
> I keep getting a critical update for SQL Server 2000 Desktop Engine(Windows)
> in Window Server 2003(KB829358), I install the update and it keeps
> redownloading the update. Can anyone help me with this issue
>

Keep getting update

I keep getting a critical update for SQL Server 2000 Desktop Engine(Windows)
in Window Server 2003(KB829358), I install the update and it keeps
redownloading the update. Can anyone help me with this issue
Hi Lloyd
Check the version you are currently on and see if it is higher than
8.00.0884, if it is then you may not need the update and might be able to
remove it by using the custom install and checking the don't show this update
option.
If you want to install it manual it can be download from
http://www.microsoft.com/downloads/d...isplaylang=en.
Also make sure that your account has enough permissions to install the
update and update the registry.
John
"Lloyd Pratt" wrote:

> I keep getting a critical update for SQL Server 2000 Desktop Engine(Windows)
> in Window Server 2003(KB829358), I install the update and it keeps
> redownloading the update. Can anyone help me with this issue
>

Keep getting update

I keep getting a critical update for SQL Server 2000 Desktop Engine(Windows)
in Window Server 2003(KB829358), I install the update and it keeps
redownloading the update. Can anyone help me with this issueHi Lloyd
Check the version you are currently on and see if it is higher than
8.00.0884, if it is then you may not need the update and might be able to
remove it by using the custom install and checking the don't show this updat
e
option.
If you want to install it manual it can be download from
http://www.microsoft.com/downloads/...displaylang=en.
Also make sure that your account has enough permissions to install the
update and update the registry.
John
"Lloyd Pratt" wrote:

> I keep getting a critical update for SQL Server 2000 Desktop Engine(Window
s)
> in Window Server 2003(KB829358), I install the update and it keeps
> redownloading the update. Can anyone help me with this issue
>