Re: memory..
From: Miha Markic [MVP C#] (miha)
Date: 04/14/04
- Next message: Anna: "DataSet.GetChanges() - problem with ListBox refreshing"
- Previous message: John: "Re: Application Speed Dilemma"
- In reply to: pvp: "memory.."
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 14 Apr 2004 15:47:02 +0200
Hi,
This is normal behaviour. By default at least one connection is open within
connection pool.
You might change the behaviour by changing connectionstring.
See
Connection Pooling for the .NET Framework Data Provider for SQL Server
.net help topic.
-- Miha Markic [MVP C#] - RightHand .NET consulting & software development miha at rthand com www.rthand.com "pvp" <anonymous@discussions.microsoft.com> wrote in message news:D89CBDD9-EFB4-41F7-BC15-4539E3CB023C@microsoft.com... > I wrote a ado.net application that uses dataadapter,connection and command objects. > I have a procedure to populate dataset.I call dispose on all objects after dataset is populate and close the connection. > I see that the application still uses connection on sqlserver(I verified this by executing sp_who on sqlserver) > application dosen't release connection untill I close the form or end the application. > I tried calling gc.collect but this did not work. > What is work around for this problem ? > Please suggest >
- Next message: Anna: "DataSet.GetChanges() - problem with ListBox refreshing"
- Previous message: John: "Re: Application Speed Dilemma"
- In reply to: pvp: "memory.."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|