Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
frankf
Starting Member
2 Posts |
 Posted - 2004-11-10 : 11:48:24
|
| I have an application on:W2K clientSql 2000 + No SPMS ODBC V3.8C++The application, running on the client, connects to SQL server for many simultaneous queries involving select, insert and update. Application creats a thread for each query. Each thread connects to the sql server via ODBC using sqlconnect. However I find that the individual thread do not close properly and stay open even after sqldisconnect has been issued on the client. At one point I have over 1200 threads on client application trying simultaneously to connect to the server and the sqlserver is holding with 276 threads open.I do not understand why the ODBC connection stays open even after sqldisconnect is issued. I have even tried disabling connection pooling, to no effect. The performance is very poor.How can I issue a large number of queries to same sql server via ODBC while guaranteeing performance? |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2004-11-10 : 12:09:49
|
| Connection pooling is a good thing. I don't think you want to disable it in this situation.-Chadhttp://www.clrsoft.comSoftware built for the Common Language Runtime. |
 |
|
|
|
|
|
Please help with SQL Server ODBC