processadmin cannot kill

We are trying to enforce some security on our SQL server,
and I am trying to move several people away from logging
on to enterprise manager with the sa user and password. I
am hoping to use Windows Authentication, but I am having
problems with a user not being able to kill processes. I
have given the user access to all of the databases and
added them to the processadmin role. They still cannot
kill processes through enterprise manager. The SQL server
itself has not been topped & restarted, but that shouldn't
be nescisary, right (?).Hi Jason,
Could you give me an explanation of what process the user would need
to kill?
Are you referring to NT Processes or SQL spids ?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi,
It is not required to stop and start sql server after giving a role. Can you
try execution the below in query analyzer to create a SQL Server login and
assign processadmin role.
sp_addlogin <Login_name>
go
sp_addsrvrolemember <login_name>,processadmin
After executing the script, login to Querry analyser using the new sql
server login.
Execute sp_who to identify the process id and execute KILL <SPID> to kill a
process.
Once you are ok with this, try killing the process from Enterprise manager
by registering using this new user.
Thanks
Hari
MCDBA
"Jason" <jeliason@.youth-guidance.org> wrote in message
news:1c7e101c4524e$e2872190$a001280a@.phx
.gbl...
> We are trying to enforce some security on our SQL server,
> and I am trying to move several people away from logging
> on to enterprise manager with the sa user and password. I
> am hoping to use Windows Authentication, but I am having
> problems with a user not being able to kill processes. I
> have given the user access to all of the databases and
> added them to the processadmin role. They still cannot
> kill processes through enterprise manager. The SQL server
> itself has not been topped & restarted, but that shouldn't
> be nescisary, right (?).|||They are SQL SPIDs as viewed under Locaks/Process IDs
under Management in Enterprise Manager. A custom
application we use sometime generates "blocking locks"
which need to be cleared by the CIS manager.
Thanks!
Jason

>--Original Message--
>Hi Jason,
> Could you give me an explanation of what process the
user would need
>to kill?
>Are you referring to NT Processes or SQL spids ?
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>