| email this FAQ to a colleague
Q: Is there a problem with Connection pooling and stored procedures? A: With connection pooling on, connections are returned to the pool, and tempdb is never freed with the connection. Therefore, before turning on connection pooling for SQL Server, it is strongly recommended that you turn off the option to create stored procedures for prepared statements. To turn off this option, double-click your store's system datasource in the ODBC Administrator in Control Panel and clear the Generate Stored Procedure for Prepared Statement check box. Important
If you turn connection pooling on and you do not turn off Generate Stored Procedure for Prepared Statement, your system may not work. For performance to improve, you must turn off Generate Stored Procedure for Prepared Statement for each ODBC datasource that the Commerce Server stores use. In addition, after you turn off the option for each datasource, you must restart IIS. - Chris Woodrow | Articles | | May 31, 1997 - Connection Pooling with ASP | | Connection pooling might be the easiest way to speed up your dynamic web pages reading from SQL Server. Unfortunately, connection pooling within is turned off by default in Active Server pages. Probably because connection pooling is rarely understood in its entirety. This issue discusses connection pooling with ASP, ISAPI, IDC, and Visual Basic applications. Included is a discussion about ODBC 3.0 and the newest bug fix for ODBC.
[Read This Article] [Top] |
|
|
