Local admin needed for DBA??

Its been proposed at my company that the DBA's no longer have WINNT Admin
rights to the SQL Servers. I don't know that Im totally opposed to it as lon
g
as I can get my job done. What things would a DBA not be able to do if he wa
s
not an Admin on the box? The two things Im really not sure of are replicatio
n
and performance monitor, but wouldnt be shocked if other people came up with
other ideas.
All thoughts are greatly appreciated.
TIA, ChrisRFull Text Search is hosed.
http://support.microsoft.com/kb/295051/en-us
There are encryption problems
http://support.microsoft.com/kb/314636/en-us
Replication will work if you use push subscriptions (change your snapshot
share from \\publisher\c$\Program Files\Microsoft SQL server\MSSQL\ReplData
to c:\Program Files\Microsoft SQL server\MSSQL\ReplData), if you are using
pull, use a non administrator share snapshot share, i.e. don't use
\\publisher\c$ rather use something like \\publisher\temp where temp maps to
c:\Program Files\Microsoft SQL server\MSSQL\ReplData.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:54D91F30-D23A-4D28-B685-AAD0AD4C654E@.microsoft.com...
> Its been proposed at my company that the DBA's no longer have WINNT Admin
> rights to the SQL Servers. I don't know that Im totally opposed to it as
> long
> as I can get my job done. What things would a DBA not be able to do if he
> was
> not an Admin on the box? The two things Im really not sure of are
> replication
> and performance monitor, but wouldnt be shocked if other people came up
> with
> other ideas.
> All thoughts are greatly appreciated.
> TIA, ChrisR|||Plus you wouldn't be able to start & stop services on the SQL boxes
(something I think every production DBA should be able to do) or
troubleshoot many O/S level problems. Setting up & troubleshooting
backup plans would become harder (but not impossible I guess) and
setting up log shipping would also become more troublesome.
Pretty much anything that deals with the O/S or filesystem on the SQL
box would become, if not impossible, more complicated to do. I'm all
for minimum-required privileges but a database administrator, I would
think, ought to be able to administer his or her database servers. I
guess it comes down to how you define "database administrator". Many
people categorise users who I would refer to as developers or analysts
as "database administrators". There's no way I would grant those type
of users local admin rights or sysadmin membership to SQL boxes. But
you need to put at least a little trust in the staff you hire to look
after your database servers methinks.
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Hilary Cotter wrote:

>Full Text Search is hosed.
>http://support.microsoft.com/kb/295051/en-us
>There are encryption problems
>http://support.microsoft.com/kb/314636/en-us
>Replication will work if you use push subscriptions (change your snapshot
>share from \\publisher\c$\Program Files\Microsoft SQL server\MSSQL\ReplData
>to c:\Program Files\Microsoft SQL server\MSSQL\ReplData), if you are using
>pull, use a non administrator share snapshot share, i.e. don't use
>\\publisher\c$ rather use something like \\publisher\temp where temp maps t
o
>c:\Program Files\Microsoft SQL server\MSSQL\ReplData.
>
>