Case Scenario: Setting up your SSAS and SSRS Servers
As you begin the process of setting up a SQL Server 2005 BI environment, you are planning out your hardware architecture. Your solution will consist of an SSRS installation that will access Online Analytical Processing (OLAP) data in SSAS built from a SQL Server data mart. Your manager has approved two blade servers for SSRS so that the service can be configured for scale-out deployment; that will help to balance the workload and will provide some load balancing. Additionally, your system administrator has set up a Network Load Balancer, NLB, to distribute the report requests. How will you handle the following two setup requirements?
- Within SSAS, you want to be able to monitor the activity on the server so that you can help tune the aggregation design and troubleshoot errors on the server. In addition, the server will be connected to a disk array to hold the OLAP data for querying, and you want all SSAS cubes and dimensions to be stored on this drive. How do you go about setting up these requirements for effective ongoing maintenance and management?
- Your SSRS implementation requires that you set up a scale-out deployment of SSRS on the two allocated servers. You have already installed the first SSRS instance on one of the servers that points to a Report Server database on your database server. You are now ready to install an instance of SSRS on the second machine. How do you use command-line operations to install and configure this instance to be part of the Web farm?
© Microsoft. All Rights Reserved.