I have a VB .DLL app that I am trying to turn off all ADO resource pooling.
I am doing this by placing the following command in my OLE DB DSN connection
string ";OLE DB Services = -4;". When I run this DLL on my development box
it performs as expceted by only holding the connections for 1 - 2 seconds.
The problem is when I install this DLL on my com+ server and re-run the
application. It then holds my connections for 60 seconds. I was under the
assumption that the DSN statement would override any settings in the reg on
the COM+ server.
Does anyone know what could be wrong? I am using VB6 and the database is
Sybase Server.
Schmidt - 28 Mar 2007 17:39 GMT
> I have a VB .DLL app that I am trying to turn off all
> ADO resource pooling...
Just curious, why would you want to do this?
Are you running into some "max-connections-limit" against
your SyBase-DBMS or is it resource-usage, or...?
Olaf
jeff - 28 Mar 2007 18:10 GMT
correct, it is a poor designed com+ object that cna use up to 20 connections
at one time due to a design flaw. We have about 75 users and since when a
connection is used and then dropped, it takes 60 seconds before the
connections can be reused. There are several other com+ objects on this
server that are also using the same Sybase DB. The Sybase DB has a max of
700 connections and when we hit the limit (caused by the design of this one
applicaiton) it crashes several apps all hitting this sybase database server.
We know the best solution is to re-write and correct the com+ objects but
that will take time and as it is we are running into a positon where we hit
the limit on connections about every 3 days.
> > I have a VB .DLL app that I am trying to turn off all
> > ADO resource pooling...
[quoted text clipped - 3 lines]
>
> Olaf
Schmidt - 28 Mar 2007 18:43 GMT
The cause that it works on your development-machine is
probably, that you then create/instantiate a "real", fresh,
unpooled Connection-Object.
In case of your COM+-environment you probably get
an already pooled Instance (no fresh one) from your
Instanciation-Call - and for such an object you can
probably not overwrite the already existing setting using
the -4.
So I see no elegant way, to work around your problem,
unless you fix all the other Sybase-Consumer Classes as
well.
Olaf
Jim Carlock - 30 Mar 2007 02:03 GMT
Not sure what's going on, but DAO might be useful with a local-
ized .mdb. Get the MDB to create links, then use a CreateTable
query inside of the Access MDB to duplicate the data tables. It
works extremily fast and if all that's going on is reading from the
tables, then you don't have to worry about sending the data
back to update the server tables and everything runs quite nicely.
It works quite well if tables aren't too big and you only need to
read only. Very fast too.

Signature
Jim Carlock
Post replies to the group.
Brian Muth - 28 Mar 2007 19:35 GMT
>I have a VB .DLL app that I am trying to turn off all ADO resource pooling.
> I am doing this by placing the following command in my OLE DB DSN
[quoted text clipped - 12 lines]
> Does anyone know what could be wrong? I am using VB6 and the database is
> Sybase Server.
I'm not sure if this is relevant, but I believe Sybase recognizes
"Pooling=False" in the connection string, and will properly close
connections immediately rather than hanging on to them.
Give that a try.
Brian
Walter Wang [MSFT] - 29 Mar 2007 03:26 GMT
Hi,
I'm not sure if it's a sybase specific issue or not. Here's a great
reference on ODBC Connection Pooling and OLEDB Session Pooling in MDAC
component:
#Support WebCast: ODBC Connection Pooling and OLEDB Session Pooling in
Microsoft Data Access Components
http://support.microsoft.com/kb/324686
To disable session pooling, besides settig Services=-4 in connection
string, youc an also disable the OLE DB session pooling by modifying the
MSDASQL registry entry for OLEDB_Services to 0xfffffffc.
For MDAC 2.1 and later, use registry key
HKEY_CLASSES_ROOT\CLSID\<Provider's CLSID>\SPTimeout to modify the session
pooling timeout. Earlier than MDAC 2.1, this value was hard coded at 60
seconds.
#INFO: OLE DB Session Pooling Timeout Configuration
http://support.microsoft.com/kb/237977
Sincerely,
Walter Wang (wawang@online.microsoft.com, remove 'online.')
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications. If you are using Outlook Express, please make sure you clear the
check box "Tools/Options/Read: Get 300 headers at a time" to see your reply
promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Walter Wang [MSFT] - 03 Apr 2007 04:52 GMT
Hi jeff,
Would you please reply here to let us know the status of this post? Thanks.
Regards,
Walter Wang (wawang@online.microsoft.com, remove 'online.')
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.