Database Reference
In-Depth Information
Chapter 8. Administering
and
Monitoring Analysis Services
In this chapter, we will cover:
• SSAS instance configuration options
• Creating and dropping databases
• Monitoring SSAS instance using Activity Viewer
• Monitoring SSAS instance using DMVs
• Cancelling a session
• Checking whether cubes are accessible
• Checking SSAS object sizes programmatically
• Backup and restore
• Synchronization
• Detaching and attaching databases
Introduction
As you have learned throughout the various chapters of this topic, SQL Server Ana-
lysis Services ( SSAS ) is a data container in its own right, separate and apart from
the SQL Server relational database engine. As such, SSAS has numerous config-
uration options, many of which alter its behavior. You can use dynamic manage-
ment views, SQL Server Profiler, Performance Monitor, and other tools to monitor and
troubleshoot SSAS activity.
If your environment has only one or a handful of SSAS instances, they can be man-
aged by the same database administrators managing SQL Server and other database
platforms. In large enterprises, there could be hundreds of SSAS instances managed
by dedicated SSAS administrators. Regardless of the environment, you should be-
come familiar with the configuration options as well as troubleshooting methodolo-
gies. In large enterprises, you might also be required to automate these tasks using
the Analysis Management Objects ( AMO ) code.
Analysis Services is a great tool for building business intelligence solutions. However,
much like any other software, it does have its fair share of challenges and limitations.
Search WWH ::




Custom Search