Export (0) Print
Expand All

Specifying Service Accounts (64-bit)

SQL Server 2000

  This topic applies only to SQL Server 2000 (64-bit).

Use the Service Account page of the Installation Wizard to specify Setup login accounts to the following Microsoft® SQL Server 2000™ services.

Service Description
SQL Server (MSSQLSERVER, or MSSQL$instancename for a named instance) Provides the core relational database functionality of SQL Server.
SQL Server Agent (SQLSERVERAGENT, or SQLAgent$instancename for a named instance) Provides the capability to schedule regular commands, schedule replication, supply a method for dealing with errors, contact SQL Server operators when errors occur, as well as other support functions.
Analysis Services (MSSQLServerOLAPService) Provides the Analysis Services engine for OLAP and data mining functionality. Although Analysis Services is installed with an instance and uses the core relational functionality provided by that instance, it is installed in a separate location and is not identified using the instance name. Analysis Services can be installed with only one instance of SQL Server 2000 (64-bit) on a server.

During Setup, you can configure these services to use one of the following Microsoft Windows® accounts:

  • Local system account

  • Local user account

  • Domain user account

You can specify the same account for all the services or a different account for each of the services. The selection you use depends on the functionality required of your SQL Server 2000 (64-bit) installation.

Local System Account

SQL Server 2000 (64-bit) can be run using the local system account if SQL Server does not require access to network resources and is not configured for replication. The following permissions must be set for the local system account for SQL Server 2000 (64-bit) to perform its tasks correctly:

For the default instance

  • Full control on the Microsoft SQL Server folder, by default:
    • systemdrive\Program Files\Microsoft SQL Server\MSSQL
  • Full control of all .mdf, .ndf, and .ldf database files.

  • Full control on the registry keys at and under:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer

    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLSERVER

For a named instance

  • Full control on the Microsoft SQL Server folder, by default:
    • systemdrive\Program Files\Microsoft SQL Server\MSSQL$instancename
  • Full control of all .mdf, .ndf, and .ldf database files.

  • Full control on the registry keys at and under the following:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQL$instancename

For the Analysis Services service

  • Full control on the Microsoft Analysis Services folder, by default:
    • systemdrive\Program Files\Microsoft Analysis Services
  • Full control on the registry keys at and under the following:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server

    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLServerOLAPService
Local User Account

If SQL Server 2000 (64-bit) is configured to use a Windows local user account, the account must fulfill the same restrictions as apply for a local system account, with the addition that it must be granted Log on as a service permission.

To create or maintain a SQL Server 2000 (64-bit) failover cluster, you must be logged on to the computer with administrator privileges; that is, you must be a member of the Administrators local group of the computer or the domain. For clustering, this means that you must be an administrator of all nodes of the cluster.

Domain User Account

Configuring SQL Server 2000 (64-bit) with a domain user account provides the greatest flexibility. Some examples of functionality provided by a domain user include:

  • Replication

  • Backing up to and restoring from network drives

  • Performing heterogeneous joins that involve remote data sources

  • Ability to define remote partitions on an Analysis server

  • Ability to process linked cubes with an Analysis server

For SQL Server 2000 (64-bit) to perform its tasks, the domain user account must be configured like the local user account discussed earlier. In addition, extended functionality is available by adding further permissions described in the following table.

Service Permission Functionality
SQL Server Network write permissions Read/Write to remote backups, data loads, and so on
SQL Server Act as part of the operating system and replace process level token Run xp_cmdshell for a user other than a SQL Server administrator
SQL Server Agent Member of the Administrators local group Create CmdExec and ActiveScript jobs belonging to someone other than a SQL Server administrator
SQL Server Agent Member of the Administrators local group Use the autorestart feature
SQL Server Agent Member of the Administrators local group Use run-when-idle jobs
Analysis Services Member of OLAP Administrators group on remote server Link to source cube on remote Analysis server
Analysis Services Permissions to data sources accessed by Analysis Services Required for processing objects

To take advantage of maximum functionality in SQL Server 2000 (64-bit), the domain user account should be a member of the Administrators local group.

If you specify a remote data storage location for Analysis Services, you must use a domain account with access to that location.

See Also

Creating Windows Service Accounts (64-bit)

Service Account (64-bit)

Show:
© 2014 Microsoft