Database Reference
In-Depth Information
Scaling out SSAS solutions
As you learned in the introductory section of this chapter, Analysis Services is tuned
for running a single query as fast as possible. This means that a single large query
can use much of the available system resources and force other queries to wait.
As a cube developer or database administrator, you need to take time to educate
users on how to best use SSAS's power without bringing the production server to its
knees. However, even fine-tuned cube design and queries leave room for scalability
issues—a single server computer can only have a finite amount of system resources
and, hence, can only serve a limited number of user requests. Additionally, you will
often find that processing and querying activities conflict with each other; much like
in any other database system, data readers can block writers and vice versa.
You have several methods at your disposal for scaling out Analysis Services solu-
tions, given as follows:
• Backup databases on the processing instance and restore the databases to
the querying instances
• Synchronize databases from the processing instances to querying instances
• Detach databases from the processing instance and attach them to querying
instances in the read-only mode
Let's learn how to implement these scale out methods while considering the benefits
and drawbacks of each.
Search WWH ::
Custom Search