Post-install Configuration (Analysis Services)
After installing Analysis Services, further configuration is required to make the server fully operational and available for general use. This section introduces the additional tasks that complete the installation. Depending on connection requirements, you might also need to configure authentication (see Connect to Analysis Services).
Later, additional work will be required once you have databases that are ready to deploy. Namely, you will need to configure role memberships on the database to grant user access to the data, design a database backup and recovery strategy, and determine whether you need a scheduled processing workload to refresh data at regular intervals. More information about database deployment and administration can be found at these links: Multidimensional Model Databases (SSAS) and Tabular Model Databases (SSAS Tabular).
Analysis Services is a replicable service, meaning you can install multiple instances of the service on a single server. Each additional instance is installed separately as a named instance, using SQL Server Setup, and configured independently to support its intended purpose. For example, a development server might run Flight Recorder or use default values for data storage that you might otherwise change on servers supporting production workloads. Another example that calls for adjusting system configuration is installing Analysis Services instance on hardware shared by other services. When hosting multiple data-intensive applications on the same hardware, you might want to configure server properties that lower the memory thresholds to optimize available resources across all of the applications.
Create an inbound rule in Windows Firewall so that requests can be routed through the TCP port used by the Analysis Services instance. This task is required. No one can access Analysis Services from a remote computer until an inbound firewall rule is defined.
During installation, you had to add at least one user account to the Administrator role of the Analysis Services instance. Administrative permissions are required for many routine server operations, such as processing data from external relational databases. Use the information in this topic to add or modify the membership of the Administrator role.
During installation, the Analysis Services service account was provisioned, with appropriate permissions to allow controlled access to program executables and database files. As a post-installation task, you should now consider whether to allow the use of the service account when performing additional tasks. Both processing and query workloads can be executed under the service account. These operations succeed only when the service account has appropriate permissions.
SQL Server Management Studio (SSMS) lets you create server groups for organizing your SQL Server instances. Scalable deployments consisting of multiple server instances are easier to manage in server groups. Use the information in this topic to organize Analysis Services instances into groups in SSMS.
During installation, you chose a server mode that determines the type of model (multidimensional or tabular) that runs on the server. If you are unsure of the server mode, use the information in this topic to determine which mode was installed.
A descriptive name can help you distinguish among multiple instances having different server modes, or among instances primarily used by departments or teams in your organization. If you want to change the instance name to one that helps you better manage your installations, use the information in this topic to learn how.
Learn how to connect to Analysis Services from Microsoft applications or custom applications using the client libraries. Depending on your solution requirements, you might also need to configure the service for Kerberos authentication. Connections that must cross domain boundaries will require HTTP access. See Connect to Analysis Services for instructions about the next steps.