Hi!
I have noticed this strange problem I cannot explain when I connect to sql
server using .net:
I use a .NET app to connect to a sql server database. When I do so, two
strange things happen at the database.
I can watch them in Enterprise Manager's Current Activity pane, and
refreshing it.
First, some times I get two Process IDs in the database, after invoking
Connection.Open call at the code. Some times, only one Process ID is
created.
Why is that?
Second, after explicity closing my connection and disposing it, at least one
Process ID remains.
**The problem happens even with Microsoft's Application Blocks samples** at
http://msdn.microsoft.com/library/de...ml/daab-rm.asp.
Only closing my app makes those Process IDs dessapear from the database.
In ASP.NET I have to kill aspnet_wp in order to clean them.
I do not use in the tests any database related object (SQLReader, Dataset,
....). You can watch this using only Connection.Open, Connection.Close and
CType(connection, IDisposable).Dispose() methods.
I have tried it on different machines with different SQL servers and
configurations.
The behavior is allways the same.
Can anyone give me a good reason for this?
Thanks in advance.
-- MC
