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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-12-02 : 08:18:11
|
| Nitin Patil writes "Hi I have application which is using SQLServer 2000 and both are installed on same machine with win2k adv. server. I am accesing SQLServer using COM+ object written in VB. Becaue my application is using the multiple threads( around 250 and many transaction from each thread ) to access the SQL server the SQL server takes lots of memory( around 400 MBRAM) and after exiting from my application it is not releasing this memory. My SQL Server is configured with default setting. i.e. dynamically manage the memory allocation? can you tell me why it is happening? is there any but in SQLServer 2000. I need to stop the sql server and start it to release the memory. I used performance monitor to objserve private bytess and it shows all of them again SQLServer.can you help me please?NitinIgentica Limitedhttp://www.igentica.com" |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2002-12-02 : 13:04:27
|
| You must have a memory leak in your application if the machine does not release the memory when you exit the application. Are you closing all of your objects in the application on exit or after you have no need for them? |
 |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2002-12-02 : 13:22:06
|
| Are you using connection pooling? If so the connections will be held open for a time.Are you running VB exe's or in debug. There was a feature where VB held connections open until the environment was closed - don't know if that still happens.Look at master..sysprocesses to see if connections are being held and by what.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
|
|
|
SQLServer 2000 and memory Problem