Starting and Stopping Services

SQL Server 2008 R2

To start or stop any Microsoft Windows service on the computer that is running Microsoft SQL Server Analysis Services, the Analysis Services administrator must be a member of the Administrators local group on the computer.

Security Note

A member of the Administrators local group has full control permissions on the computer that is running Analysis Services and can perform any task on that computer, such as reading the data stored in any Analysis Services instance on the computer.

The services used by Analysis Services can be started manually as needed, or can be started automatically when Windows starts. The following table lists the various services used by Analysis Services and when each of these services must be started.

Service

When to start

Analysis Services

(Default instance name: MSSQLServerOLAPService

Named instance name: MSOLAP$InstanceName)

An instance of Analysis Services must be started before users can log on to that instance.

SQL Server

(Default instance name: MSSQLServer

Named instance name: MSSQL$InstanceName)

If the Analysis Services relational store is stored in SQL Server, or if writeback has been configured to SQL Server, the SQL Server service hosting the relational data must be started before Analysis Services can access the data in the relational store or writeback data to the relational store.

SQL Server Agent

(Default instance name: SQLServerAgent

Named instance name: SQLAgent$InstanceName)

If SQL Server Agent is configured to execute automated tasks, SQL Server Agent for the appropriate SQL Server instance must be started.

SQL Server Browser

(Service name:

SQL ServerBrowser )

If users need to connect to a named instance of Analysis Services without specifying a port number, SQL Server Browser must be started.

An administrator generally sends a message to connected users before stopping a service. The message indicates exactly when the instance will be stopped (shutdown) completely. This shutdown message allows the currently connected users to complete their tasks before the instance is stopped. New users should not connect during this time and new jobs should not be started.