![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
can someone please clarify the connection pooling feature that comes with ADOConPool ? I was able to run the sample code below just fine, i ran the program below a few times with a few seconds in between the runs, but when I check the application events using the event viewer (after making the necessary changes to the registry to record olap open and close connections), i notice that there is a pair of open and close events with no delay for every program run, in other words, the connection is not being pooled between application runs, i've checked the MaxSession (32) and Timeout (300) properties, and the defaults seems fine, am i misunderstanding how connection pooling here works ? if so, is there any way to obtain the benefits of connection pooling on a webpage that queries an analysis services without caching the connection object in an Application object ? Caching the connection object in a application object i believe would serialize all request to the web application and i would like to avoid that sample code: Private Sub Command1_Click() Dim objconnpool As MSXmlAnalysisSCLib.ADOConPool Dim objconn As ADODB.Connection strtmp = "Data Source=localhost;Provider=MSOLAP.2;Trusted_Connect ion=yes;Initial Catalog=FoodMart 2000" Set objconnpool = New MSXmlAnalysisSCLib.ADOConPool Set objconn = objconnpool.GetConnection(strtmp) objconnpool.ReturnConnection objconn Set objconnpool = Nothing Set objconn = Nothing End Sub |
![]() |
| Thread Tools | |
| Display Modes | |
| |