Data | database | Performance If your ASP application interacts with the database (I want to definitely have access to the database, or what do I do with ASP?), using the connection buffer pool will greatly improve the performance of the database. The time and system resources spent in establishing a connection to the data are not trivial. When each page that needs to establish a database connection instance is accessed, a new connection object is created and destroyed after the page has been executed, and if there are many people visiting your site at the same time, the visitor will find that the system performance becomes very low.
The connection buffer pool maintains the connection instance so that users can use the database connection at any time. For example, you have an ASP page that creates a connection to a SQL database, takes some data out of the database, and displays it on a Web page. If the connection buffer pool is not turned on, the ASP will work like this:
Create a database connection
Submitting a query request to a database
Get Data
Display data
Destroy connection
Each time a user clicks on the page, the server performs these actions. However, when you enable the connection buffer pool, the following steps are related:
To see if there are any unused connections in the buffer pool
If so, use the connection, and if not, create a new connection
Submitting a query request to a database
Get Data
Display data
Returning the connection to the buffer pool
When a page needs to establish a database connection, reusing a connection can save a lot of system resources.
Now let's look at how to get the ASP application to use the connection buffer pool. First, you have to open the connection buffer pool in the registry's ASP registry, and then set SQL Server to use TCP/IP Sockets.
To enable the connection buffer pool in the registry, you have to run Regedit to locate this registry key:
Hkey_local_machine\system\currentcontrolset\services\w3svc\asp\paramet
ERs
(If you don't have this key, build one yourself)
Find the Startconnectionpool key and change the key value from 0 to 1. After this change, ADO and ASP will enable the connection buffer pool.
The final step is to set SQL Server to use TCP/IP Sockets. Start SQL Server Manager and set the default network setting to TCP/IP Sockets. (Note: The connection buffer pool is not valid for ASP applications with access as the background database.)
