sp_who2

#1

When I run sp_who2 I am seeing about a dozen spid's using
the sa login running in the background and the command is
Task Manager. Does anyone know why this is and would it
hurt to kill those spid's? The lastbatch date for each
spid is over 1 month old.

#2

Use EM to check if these sid's r still Active.. And see what Command is
running.. And has any object locks ..

According to these things kill or let alive

"Robert" <anonymous (AT) discussions (DOT) microsoft.com> wrote

Quote:

When I run sp_who2 I am seeing about a dozen spid's using
the sa login running in the background and the command is
Task Manager. Does anyone know why this is and would it
hurt to kill those spid's? The lastbatch date for each
spid is over 1 month old.

#3

And what is the command in sp_who2?

There are system processes that will be running very
validly under sa. Examples are

Log writer
lock monitor
lazy writer
signal handler

etc
etc

Quote:

-----Original Message-----
When I run sp_who2 I am seeing about a dozen spid's using
the sa login running in the background and the command is
Task Manager. Does anyone know why this is and would it
hurt to kill those spid's? The lastbatch date for each
spid is over 1 month old.
.

#4

The command is Task Manager

Quote:

-----Original Message-----
And what is the command in sp_who2?

There are system processes that will be running very
validly under sa. Examples are

Log writer
lock monitor
lazy writer
signal handler

etc
etc

-----Original Message-----
When I run sp_who2 I am seeing about a dozen spid's
using
the sa login running in the background and the command
is
Task Manager. Does anyone know why this is and would it
hurt to kill those spid's? The lastbatch date for each
spid is over 1 month old.
.

.

#5

Please forgive my ignorance but how do you check active
spid's in EM?

Quote:

-----Original Message-----
Use EM to check if these sid's r still Active.. And see
what Command is
running.. And has any object locks ..

According to these things kill or let alive

"Robert" <anonymous (AT) discussions (DOT) microsoft.com> wrote in
message
news:294201c4a1af$5bfcf630$a601280a (AT) phx (DOT) gbl...
When I run sp_who2 I am seeing about a dozen spid's
using
the sa login running in the background and the command
is
Task Manager. Does anyone know why this is and would it
hurt to kill those spid's? The lastbatch date for each
spid is over 1 month old.

.

#6

Leave it alone then

--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com

"Robert" <anonymous (AT) discussions (DOT) microsoft.com> wrote

Quote:

The command is Task Manager
-----Original Message-----
And what is the command in sp_who2?

There are system processes that will be running very
validly under sa. Examples are

Log writer
lock monitor
lazy writer
signal handler

etc
etc

-----Original Message-----
When I run sp_who2 I am seeing about a dozen spid's
using
the sa login running in the background and the command
is
Task Manager. Does anyone know why this is and would it
hurt to kill those spid's? The lastbatch date for each
spid is over 1 month old.
.

.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

sp_who2

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts

sp_who2 - 09-23-2004 , 03:53 PM

Re: sp_who2 - 09-24-2004 , 02:37 AM

sp_who2 - 09-24-2004 , 08:27 AM

sp_who2 - 09-24-2004 , 11:14 AM

Re: sp_who2 - 09-24-2004 , 11:15 AM

Re: sp_who2 - 09-25-2004 , 06:14 AM