Luke's approach makes good sense; take the onus off the DBA's . . . then
let the auditors come.
-----Original Message-----
From: Luke Kevin
[mailto:mssqldba-ezmlmshield-x95718271.[Email address protected]
Sent: Monday, October 30, 2006 4:08 PM
To: LazyDBA Discussion
Subject: RE: Applications requiring SysAdmin Privilages
Our shop has shared SQL Server boxes that are used to host our SQL
Server apps. We install all "well-behaving" applications in our shared
SQL server environment with no cost to the business area. Applications
that require SA rights are not allowed into our shared (free)
environment, and are not supported by our internal DBA group. That
means that if it breaks, we're not responsible, we do not perform
Maintenance jobs (backups, reorgs, etc), and we do not monitor the
servers.
-----Original Message-----
From: Anthon Mark J - DOA
[mailto:mssqldba-ezmlmshield-x18879413.[Email address protected]
Sent: Monday, October 30, 2006 1:37 PM
To: LazyDBA Discussion
Subject: RE: Applications requiring SysAdmin Privilages
Very apropos; this actually came up today in our group. We had to grant
"sysadmin" in order for the vendor application service to start.
However, we never want to grant "sysadmin" either; this will be an
agenda item for our next staff meeting. We're hoping that a work around
can be found granting lesser privileges.
-----Original Message-----
From: Yvonne Tingstad
[mailto:mssqldba-ezmlmshield-x90071305.[Email address protected]
Sent: Monday, October 30, 2006 12:11 PM
To: LazyDBA Discussion
Subject: Applications requiring SysAdmin Privilages
Hey all
I would like to know how all of you handle this situation. What do you
do when you have user applications (in our case, IT) that required Sys
Admin privileges to the Sql Server but there isn't any documentation nor
has support calls to the vendor allowed us to find out why that
privilege is required? In fact, we have one application where the vendor
states up and down that sys admin privileges are not required, however
we cannot get the application to fully work without it.
I have a policy that sys admin privileges will not be granted to any
application user in our production environment. This has caused a
number of MSDE instances to pop up in order to get around this. This
isn't the right solution either as administrating these instances is a
pain.
What do you do within your shops?
Yvonne
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the
Baytex Energy Helpdesk at [Email address protected]
**********************************************************************
---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a
dba job: http://jobs.lazydba.com To subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a
dba job: http://jobs.lazydba.com To subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a
dba job: http://jobs.lazydba.com To subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
MS Sql Server LazyDBA home page