Re: Managing OLAP Connections
- From: Jéjé <willgart@xxxxxxxxxxxxxxxxx>
- Date: Mon, 5 Sep 2005 14:34:49 -0400
don't close the session, close the connection but not the session. save the session ID to reuse it when the user ask the cube again. Try to find some solution to use the connection pooling feature.
optimize the connection string by using cache ratio=0.001;cache ratio2=0.001;cache policy=7;non empty threshold=1
force the query execution to the server level.
"billd" <billd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:FEA14F98-AE26-4F71-8B17-9A7A4DA4E451@xxxxxxxxxxxxxxxx
Hi have an ASP.Net application that allows multiple users to query against a
cube. I am using ADOMD.Net to make the queries.
Based on what I have read to be best practice, when an ASP page makes a
query I create the connection, make the query and then close the connection.
The connection string is always exactly the same so as to take advantage of
connection pooling.
The problem is that opening, querying and then closing results in slow
performance - about 3 seconds each time. If I keep the connection open in a
Session variable, subsequent queries take under 1/2 second.
Since connections are limited resources and I need my application to scale,
keeping connections in user Sessions is not desirable.
Can anyone offer some advice on how to get good performance with not dedicating connections?
Thanks,
Bill
.
- References:
- Managing OLAP Connections
- From: billd
- Managing OLAP Connections
- Prev by Date: msolap80 provider error with VB6 COM+ Dll
- Next by Date: Re: Write back (again..)
- Previous by thread: Managing OLAP Connections
- Next by thread: msolap80 provider error with VB6 COM+ Dll
- Index(es):
Relevant Pages
|
