Re: SQL admin versus Windows admin
- From: "Mike C#" <xyz@xxxxxxx>
- Date: Sun, 9 Mar 2008 00:40:34 -0500
"Bill Prentice" <BillPrentice@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EE796260-8186-4247-88FC-054BB6F91301@xxxxxxxxxxxxxxxx
I have a situation where I'm needing to set up a SQL server for use by a
couple of SQL programmers. The problem is that I want to give them enough
access to be able to do the important day-to-day things
(start/stop/restart
SQL services, fully admin the SQL databases, etc.) without giving them
full
control over the server.
I know that a large portion of what they need can be done via the rights
on
SQL itself - it's the non-SQL Windows components I'm wanting to retain
sole
admin rights over.
Does anyone know of any white papers/articles/etc that can get me started
in
the right direction?
On the SQL side you could apparently just make them system admins and that
would do the trick there. On the Windows side you'll need Windows-specific
rights info. A quick Google of "Windows start stop services" turned up
several hits, including this article:
http://www.windowsitpro.com/article/articleid/48881/letting-a-user-start-and-stop-services-without-granting-the-user-administrator-privileges.html
("Letting a User Start and Stop Services Without Granting the User
Administrator Privileges").
Not sure what other important "day-to-day things" you have in mind, but it
sounds like Windows-specific privileges issues. You might try Googling and
posting to Windows-specific newsgroups like
"Microsoft.Public.Windows.Server.Security", etc.
.
- Prev by Date: Re: application roles
- Next by Date: user permissions
- Previous by thread: encryption key management
- Next by thread: user permissions
- Index(es):
Relevant Pages
|
|
