SQL Server Customer Advisory Team - SQL Server Best Practices

Enabling SQL Server customers to navigate the most challenging frontiers of large scale data management.

ToolBox

ASLB Toolkit

Author: Carl Rabeler

Contributor: Josh Caplan

Reviewers: Prem Mehra, Denny Lee, John Desch, Wayne Robertson, Steve Pontello, Thomas Kejser

The ASLB toolkit is a custom Analysis Services load balancing solution that consists of a load balancing Web service backed by a SQL Server load balancing metadata database to load balance MDX queries across multiple query servers. The metadata database contains information about each Analysis Services query server to which queries can be redirected by the Web service.

Load Balancing Web Services

Location of the Analysis Services load balancing (ASLB) Web application. Internet Information Services (IIS) is required on these servers. These servers can use Network Load Balancing (NLB) for failover.  For more information about using Network Load Balancing, see Network Load Balancing Deployment Guide.

Load Balancing metadata db

Location of ASLB database. The ASLB database can be mirrored for failover (optional, but recommended for availability). For more information about mirroring, see Database Mirroring Best Practices and Performance Considerations.

AS servers with IIS and MSMDPump

Location of Microsoft® SQL Server® Analysis Services databases. IIS and MSMDPump.DLL must be installed on each of these servers.

 

 

 

 

 

 

 

 

Important: For more information, including a discussion of the problems that are solved by ASLB that are not solved by other software and hardware load balancing solutions, see the Microsoft SQL Server 2008 Analysis Services Consolidation Best Practices paper on the SQLCAT web site.

To Get Started: Download the setup instructions and solution files at: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c7737e80-8dfd-4cb6-a27e-69bbe03b2f9e 

Comments

 

CarlRabeler said:

On Page 14, in section 4.1.4, it should read "“Change the property values for the connectionString properties for your environment by replacing the Server1 and Server2 placeholders with the SQL Server server names" not the Analysis Services server names

August 25, 2010 12:29 PM

About CarlRabeler

Carl is a Senior Program Manager on the SQL Server Customer Advisory Team, and is an Extended Customer Program Manager with the Reporting Services and Integration Services product groups. Carl works closely with internal and external customers to develop solutions and validate SQL Server business intelligence best practices for working with large scale and complex BI solutions. Carl has worked with Microsoft SQL Server for over 13 years as a consultant, mentor, writer, speaker and trainer. Carl has written several SQL Server books and numerous technical white papers, has presented at many SQL Server conferences, and has provided mentoring and consulting services for numerous companies around the world.
sql, server, best practices, whitepapers, analysis services, data mining, olap, datawarehouse, datawarehousing, availability, clustering, capacity, collation, data types, data warehouse, database, design, index, mirroring, optimization, partitions, performance, precision, processing, querying, scalability, security, reporting services, integration services
Copyright 2008 Microsoft Corporation. All Rights Reserved.