How to Kill Process - Sleeping, Awaiting Command

Hi,
Any help will me be much apprecaited. Our SQL Server 2000
has many processing as Awaiting Command, Sleeping which
we can't seen to kill even server restart doesn't get rid
of them.
How do I kill them?
Hw do I avoid process going in that state in the future?
All these processes below to a user name which we use to
run some stored procedure.
Please also email your reply to terryb@.tisc.edu.au.
Thank you
TerryTerry
Please refer to KILL command on BOL
"Terry Bhatti" <terryb@.tisc.edu.au> wrote in message
news:01cf01c37120$72997e60$a001280a@.phx.gbl...
> Hi,
> Any help will me be much apprecaited. Our SQL Server 2000
> has many processing as Awaiting Command, Sleeping which
> we can't seen to kill even server restart doesn't get rid
> of them.
> How do I kill them?
> Hw do I avoid process going in that state in the future?
> All these processes below to a user name which we use to
> run some stored procedure.
> Please also email your reply to terryb@.tisc.edu.au.
> Thank you
> Terry
>|||Terry,
When you say you can't seem to kill them, are you referring to the KILL
command failing?
Are these connections autostarting when you start the SQL Server? How is it
that the problem is still there after a server restart? Try using DBCC
INPUTBUFFER(spid) to see if you can figure out what is going on.
Awaiting Command and Sleeping are not pernicious states for a connection to
be in.
Russell Fields
"Terry Bhatti" <terryb@.tisc.edu.au> wrote in message
news:01cf01c37120$72997e60$a001280a@.phx.gbl...
> Hi,
> Any help will me be much apprecaited. Our SQL Server 2000
> has many processing as Awaiting Command, Sleeping which
> we can't seen to kill even server restart doesn't get rid
> of them.
> How do I kill them?
> Hw do I avoid process going in that state in the future?
> All these processes below to a user name which we use to
> run some stored procedure.
> Please also email your reply to terryb@.tisc.edu.au.
> Thank you
> Terry
>