Using Profiler Causes SQL Connection pool to become exceeded

Use this forum for questions on how to use .NET Memory Profiler and how to analyse memory usage.
Post Reply
sahaine
Posts: 2
Joined: Fri Feb 23, 2007 1:57 pm

Using Profiler Causes SQL Connection pool to become exceeded

Post by sahaine » Fri Feb 23, 2007 2:01 pm

I have an application(Servcice) that will connect to a database collect some data and then disconenct(Simple) however when i run it with the memory profiler i find that there are no connections in the pool to use!!!

Andreas Suurkuusk
Posts: 1029
Joined: Wed Mar 02, 2005 7:53 pm

Post by Andreas Suurkuusk » Sun Feb 25, 2007 10:35 pm

I don't completely understand what problem you are having, but the profiler should not affect the way SQL connections work.

Is it possible for you to provide some additional information? Maybe you can provide some code that demonstrates the problem?
Best regards,

Andreas Suurkuusk
SciTech Software AB

sahaine
Posts: 2
Joined: Fri Feb 23, 2007 1:57 pm

Post by sahaine » Mon Feb 26, 2007 10:22 am

I think the problem lies within the monitoring of Unamanged Code and the SQL connection object uses unmanged code. I have emailed SciTech regarding this and once we have evaluated the problems /solution i will post the resutls.

Post Reply

Who is online

Users browsing this forum: No registered users and 27 guests