Microsoft Knowledge Base Email Alertz

KBAlertz.com: This article explains how you can prevent Microsoft Windows NT system administrators from having system administrator (sa) privileges in SQL Server.

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **


Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.


Community Site



We Send hundreds of thousands of emails using ASP.NET Email



Expert Web Design & Graphic Design
Design44.com

ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 263712 - Last Review: April 7, 2006 - Revision: 7.2

How to impede Windows NT administrators from administering a clustered instance of SQL Server

This article was previously published under Q263712

On This Page

SUMMARY

This article explains how you can impede Microsoft Windows system administrators from having system administrator permissions in Microsoft SQL Server, Enterprise Edition.

MORE INFORMATION

By default, SQL Server Setup creates the BUILTIN\Administrators login, and then adds the login to the "Sysadmin" fixed server role. This change grants system administrator permissions to any account in the Local Administrators group. In some environments, you might not want to permit Microsoft Windows system administrators to have this kind of access to SQL Server. On a stand-alone computer that is running SQL Server, you can remove the BUILTIN\Administrators login from SQL Server and limit this type of access.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
237604  (http://kbalertz.com/Feedback.aspx?kbNumber=237604/ ) SQL Server Agent does not start and displays error 18456
291255  (http://kbalertz.com/Feedback.aspx?kbNumber=291255/ ) BUG: IsAlive check does not run under the context of the BUILTIN\Administrators account in SQL Server 2000 Enterprise Edition
295034  (http://kbalertz.com/Feedback.aspx?kbNumber=295034/ ) FIX: Microsoft Search Service may cause 100% CPU usage if BUILTIN\Administrators login is removed
274446  (http://kbalertz.com/Feedback.aspx?kbNumber=274446/ ) Upgrade to SQL Server 2000 failover solution recommended for all non-SQL Server 2000 virtual servers


On a SQL Server cluster, you can remove the BUILTIN\Administrators group if the following conditions are true:
  • Before you run the Cluster Wizard, you must create the cluster service account as a login in SQL Server. This account does not need to be a member of the "Sysadmin" fixed server role. This account just needs to be able to connect and to do the "IsAlive" check.

    For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
    291255  (http://kbalertz.com/Feedback.aspx?kbNumber=291255/ ) BUG: IsAlive check does not run under the context of the BUILTIN\Administrators account in SQL Server 2000 Enterprise Edition
  • Before you run the Cluster Wizard, you must create the service accounts for SQL Server Agent and SQL Server and make these accounts members of the Sysadmin fixed server role.
  • If the SQL Server cluster is on a computer that is running Microsoft Windows 2000 and you are running a full-text search, you can remove the BUILTIN\Administrators group if the NT Authority\System account is a member of the Sysadmin fixed server role.
Note The Cluster Wizard only exists in SQL Server 7.0. Therefore, if you are using SQL Server 2000 or SQL Server 2005, ignore the references to the Cluster Wizard in these conditions.

SQL Server 6.5 and SQL Server 7.0

To limit access for Microsoft Windows NT Administrators as system administrators on a SQL Server cluster, follow these steps:
  1. Explicitly add the account that is being used for the cluster service as a SQL Server login. You must assign the "Sysadmin" role to this login.

    Note If the computer that is running SQL Server is unclustered and then reclustered, you must repeat this process.
  2. Remove the BUILTIN\Administrators login from the computer that is running SQL Server after the SQL Server Failover Cluster Wizard successfully clusters the SQL Server installation.

SQL Server 2000 and SQL Server 2005

To limit access for Windows NT Administrators as system administrators on a SQL Server cluster, follow these steps:
  1. Explicitly add the account that is being used for the cluster service as a SQL Server login. You do not need to assign the "Sysadmin" role to this login.
  2. If a full-text search will be used on the cluster, you must add the [NT Authority\System] account to the server's "sysadmin" group. For example, you can use the following sample code:
    Grant [NT Authority\System] a login to SQL Server:
    EXEC sp_grantlogin [NT Authority\System]
    Add that account to the sysadmins role:
    EXEC sp_addsrvrolemember @loginame = [NT Authority\System] 
    , @rolename =  'sysadmin'
    					
  3. Remove the BUILTIN\Administrators login from SQL Server after you install the virtual server.

APPLIES TO
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 7.0 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise Edition
Keywords: 
kbsql2005cluster kbinfo KB263712
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please