Re: Processadmin problems
From: Russell Fields (RussellFields_at_NoMailPlease.Com)
Date: 09/17/04
- Next message: Steve Thompson: "Re: User defined role in master database doesn't work . Please Help!!!"
- Previous message: Russell Fields: "Re: User defined role in master database doesn't work . Please Help!!!"
- In reply to: Steve Gutzwiller: "Processadmin problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 17 Sep 2004 14:43:06 -0400
Steve,
Enterprise Manager was written a little earlier than some of the function
and roles that exist now. I am unsurprised that this does not work for you.
EM (based on the old logic) checks that you are not sysadmin and grays out
the option, all in an effort to be friendly. (It will all be better in
2005.) This is not the only thing in EM that is not fully up-to-date.
FWIW - I personally always use Query Analyzer to issue KILLs. I do
understand the complexity for your support people. However, EM is also not
the quickest way to look at processes. There are system stored procedures,
and many home-grown variants, to focus on blockers, lockers, and "active
sleepers" and give you a quicker look at what is really going on.
Russell Fields
"Steve Gutzwiller" <steveg@payerpath.com> wrote in message
news:ecb91641.0409170628.6d2b1a9b@posting.google.com...
> Hi all,
>
> I have a SQL login which is used by an application to access data on
> our server as well as by support personnel for the application. The
> support staff regularly accesses our databases to research and resolve
> application issues as well as killing orphaned connections, blocking
> processes, etc.
>
> This login had been a member of the sysadmin fixed server role but I
> recently reduced its rights to being a member of the processadmin
> fixed server role plus mapping to dbo in each of the applicable
> databases. Our application continues to run fine and the support
> staff can access the databases normally. However, the support folks
> are no longer able to kill SPIDS using SQL Server Enterprise Manager.
> They can see the SPIDs under Current Activity - Process Info but the
> "Kill Process" context menu option is grayed out any can't be used.
>
> As a workaround, they're currently using Query Analyzer to issue the
> KILL statements to the server which works fine so I know I have the
> login is configured properly. This isn't a great solution thought as
> now they have to use two tools to do their job whereas before, they
> could just use Enterprise Manager.
>
> Can anyone shed some light on this behavior of Enterprise Manager? Is
> anyone aware of a way of getting this functionality back in Enterprise
> Manager without granting sysadmin access? Thanks for your help.
>
>
> Steve Gutzwiller
> SQL Server DBA
- Next message: Steve Thompson: "Re: User defined role in master database doesn't work . Please Help!!!"
- Previous message: Russell Fields: "Re: User defined role in master database doesn't work . Please Help!!!"
- In reply to: Steve Gutzwiller: "Processadmin problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
