| DotNetFirebird Using Firebird SQL in .NET. |
|
Home
Features
Download
Documentation
FAQ
Tools and Code
About
Blog
|
Wednesday, February 16, 2005
Connection PoolingFirebird ADO.NET provider supports connection pooling. By default, connection pooling is turned on. That means that when you call Close method on FbConnection instance the connection to the server is not closed but is returned to the pool. Connection pooling is useful especially for Web applications. Each page request would otherwise need to open a new connection and that can be time expensive. You can modify the behavior of connection pooling in the connection string by using these parameters:
Since version 1.7 of the Firebird ADO.NET Provider you can check the number of connections in the pool using FbConnection.GetPooledConnectionCount(). You can explicitly clear a pool using FbConnection.ClearPool() or all pools using FbConnection.ClearAllPools(). Things to remember:
Comments:
hello,
i don't know if it's a bug but it may be usefull for other developer. i'm using DotNetFirebird with a win2000/IIS 5 webserver. This webserver is located on the "orange (DMZ)" network of a linux/IPCop firewall. My DB server is not firebird but Interbase open v6, located on the "green (local)" network. The connection string for dotnet provider contain the IP address of this DB server, database name and username/password only. On the IPCop machine i've configured a pinhole to allow DMZ webserver to connect to my DB server (TCP port 3050). When i use this configuration, it take 10 seconds to connect to the DB. After one day of verification of my code, i've added a 2nd pinhole from DMZ to DB server on port 137 (NetBios - NS). And now it take less than two seconds to connect to the database. Well, may a bug of IIS, IPCop, Interbase or dotnet provider... i wish it could help someone. Blog comments are closed.
Previous
Archives
Copyright © 2005 - 2007 DotNetFirebird |