Jaa


Connection Pooling for Analysis Services Datasource in Reporting Services

Problem description

====================

I just wanted to write about how reporting services manages connections with Analysis Services Data Source. Reporting Services, when connecting to Analysis Services as a data source initiates a separate connection for each user and each query. Once the data is returned, the connection is closed by the Reporting Services client, so there is no connection pooling  when using Analysis Services as a data source. As a principle of Reporting Services connecting to analysis Services, It opens a connection->runs query->retrieves result->Closes Connection.

I run profiler trace and saw following behaviour for every report render request.

clip_image001

Conclusion, Reporting Services opens new connection for each request and closes this connection at the end of request.Since Reporting Services uses ADOMD.NET and ADOMD.NET doesn’t support connection pooling

Comments

  • Anonymous
    October 07, 2010
    Hi, So, Is it not possible to use pooling at all? Is there no setting where I can say something like "please, use connection pool" since I have defined as Share Data Source to connect to a SSAS Cube