Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
ADO Connection won't close
Message
De
13/02/2003 13:33:31
Jorge Haro
Independent Consultant
Juarez, Mexique
 
 
À
13/02/2003 12:54:17
Information générale
Forum:
Visual FoxPro
Catégorie:
Client/serveur
Divers
Thread ID:
00752453
Message ID:
00752823
Vues:
17
Hi Brad, I was suspecting it was something like that, I did do a little research about it yesterday, although I'm not that big of a fan of searching through MSDN, I end up going in circles <g>, but that's my problem I guess. I did learn that SQL Server uses connection pooling by default. Searching for those terms you suggested does give more precise information, I suppose it's just a matter of knowing exactly what you're looking for.

What really gets my attention is the fact that the behaviour varies if I add the Wait before showing the messagebox. My main concern was using more connections than necessary since I'm working with disconnected recordsets, and the application is supposed to work with MSDE, the connections in question (if they turned out to be open, which apparently is not so) would still be idle so I doubt they'll create any performance problems in MSDE.

>Hi Jorge,
>You are most likely seeing connection pooling but there are several types of pooling. Search the MS Knowledge Base for "Connection Pooling" and "OLE DB Services"
>Thanks!
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform