|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
sp_who2 shows old connectionswhen I tried sp_who2, I see connections that are old, please take a look at this and suggest what I need to do - (I have connections showing up since 6/27), how can I clean them up and how did it stay so long? SPID Status Login HostName BlkBy DBName Command CPUTime DiskIO LastBatch ProgramName SPID ----- ------------------------------ -------------------------------------- ------------- ----- ------------- ---------------- ------- ------ -------------- ---------------------------------------------- ----- 1 BACKGROUND sa . . NULL LAZY WRITER 1313 0 06/27 11:56:20 1 2 sleeping sa . . NULL LOG WRITER 30922 0 06/27 11:56:20 2 3 BACKGROUND sa . . master SIGNAL HANDLER 0 0 06/27 11:56:20 3 4 BACKGROUND sa . . NULL LOCK MONITOR 438 0 06/27 11:56:20 4 5 BACKGROUND sa . . master TASK MANAGER 0 23 06/27 11:56:20 5 6 BACKGROUND sa . . master TASK MANAGER 391 0 06/27 11:56:20 6 7 sleeping sa . . NULL CHECKPOINT SLEEP 766 1074 06/27 11:56:20 7 9 BACKGROUND sa . . master TASK MANAGER 0 0 06/27 11:56:20 9 10 BACKGROUND sa . . master TASK MANAGER 0 0 06/27 11:56:20 10 11 BACKGROUND sa . . master TASK MANAGER 0 27 06/27 11:56:20 11 12 BACKGROUND sa . . master TASK MANAGER 0 24 06/27 11:56:20 12 51 sleeping NT AUTHORITY\SYSTEM webDB . msdb AWAITING COMMAND 163797 55 07/14 16:41:31 SQLAgent - Alert Engine 51 Hi,
Those connections were system processes. 06/27 will be the date you started the SQL Server service. No worries, these processes are used by SQL Server Engine to writeE all the commited pages to Disk if the size of the free buffer list is less/Handling scheduled task/Monitoring Locks/Checkpoint operation ... Thanks Hari SQL Server MVP Show quote "Mike" <M***@discussions.microsoft.com> wrote in message news:FE55E240-D2AA-4EBF-8F4D-92F9C96E715C@microsoft.com... > Hi, > when I tried sp_who2, I see connections that are old, please take a look > at > this and suggest what I need to do - (I have connections showing up since > 6/27), how can I clean them up and how did it stay so long? > > SPID Status Login > HostName BlkBy DBName Command CPUTime DiskIO > LastBatch > ProgramName SPID > ----- ------------------------------ -------------------------------------- > ------------- ----- ------------- ---------------- ------- ------ > -------------- ---------------------------------------------- ----- > 1 BACKGROUND sa > . . NULL LAZY WRITER 1313 0 06/27 > 11:56:20 1 > 2 sleeping sa > . . NULL LOG WRITER 30922 0 06/27 > 11:56:20 2 > 3 BACKGROUND sa > . . master SIGNAL HANDLER 0 0 06/27 > 11:56:20 3 > 4 BACKGROUND sa > . . NULL LOCK MONITOR 438 0 06/27 > 11:56:20 4 > 5 BACKGROUND sa > . . master TASK MANAGER 0 23 06/27 > 11:56:20 5 > 6 BACKGROUND sa > . . master TASK MANAGER 391 0 06/27 > 11:56:20 6 > 7 sleeping sa > . . NULL CHECKPOINT SLEEP 766 1074 06/27 > 11:56:20 7 > 9 BACKGROUND sa > . . master TASK MANAGER 0 0 06/27 > 11:56:20 9 > 10 BACKGROUND sa > . . master TASK MANAGER 0 0 06/27 > 11:56:20 10 > 11 BACKGROUND sa > . . master TASK MANAGER 0 27 06/27 > 11:56:20 11 > 12 BACKGROUND sa > . . master TASK MANAGER 0 24 06/27 > 11:56:20 12 > 51 sleeping NT AUTHORITY\SYSTEM > webDB . msdb AWAITING COMMAND 163797 55 07/14 > 16:41:31 SQLAgent - Alert Engine 51 Thanks Hari,
Can you point me to a good article where I can understand sp_who2 better. I want to learn to use this feature. Show quote "Hari Prasad" wrote: > Hi, > > Those connections were system processes. 06/27 will be the date you started > the SQL Server service. > No worries, these processes are used by SQL Server Engine to writeE all the > commited pages to Disk if the size of the free > buffer list is less/Handling scheduled task/Monitoring Locks/Checkpoint > operation ... > > Thanks > Hari > SQL Server MVP > > "Mike" <M***@discussions.microsoft.com> wrote in message > news:FE55E240-D2AA-4EBF-8F4D-92F9C96E715C@microsoft.com... > > Hi, > > when I tried sp_who2, I see connections that are old, please take a look > > at > > this and suggest what I need to do - (I have connections showing up since > > 6/27), how can I clean them up and how did it stay so long? > > > > SPID Status Login > > HostName BlkBy DBName Command CPUTime DiskIO > > LastBatch > > ProgramName SPID > > ----- ------------------------------ -------------------------------------- > > ------------- ----- ------------- ---------------- ------- ------ > > -------------- ---------------------------------------------- ----- > > 1 BACKGROUND sa > > . . NULL LAZY WRITER 1313 0 06/27 > > 11:56:20 1 > > 2 sleeping sa > > . . NULL LOG WRITER 30922 0 06/27 > > 11:56:20 2 > > 3 BACKGROUND sa > > . . master SIGNAL HANDLER 0 0 06/27 > > 11:56:20 3 > > 4 BACKGROUND sa > > . . NULL LOCK MONITOR 438 0 06/27 > > 11:56:20 4 > > 5 BACKGROUND sa > > . . master TASK MANAGER 0 23 06/27 > > 11:56:20 5 > > 6 BACKGROUND sa > > . . master TASK MANAGER 391 0 06/27 > > 11:56:20 6 > > 7 sleeping sa > > . . NULL CHECKPOINT SLEEP 766 1074 06/27 > > 11:56:20 7 > > 9 BACKGROUND sa > > . . master TASK MANAGER 0 0 06/27 > > 11:56:20 9 > > 10 BACKGROUND sa > > . . master TASK MANAGER 0 0 06/27 > > 11:56:20 10 > > 11 BACKGROUND sa > > . . master TASK MANAGER 0 27 06/27 > > 11:56:20 11 > > 12 BACKGROUND sa > > . . master TASK MANAGER 0 24 06/27 > > 11:56:20 12 > > 51 sleeping NT AUTHORITY\SYSTEM > > webDB . msdb AWAITING COMMAND 163797 55 07/14 > > 16:41:31 SQLAgent - Alert Engine 51 > > >  |
|||||||||||||||||||||||
Other interesting topics