Debugging a .net application makes an sql server hang

Hello everyone,
I have been debugging a module I have coded using the VS.NET debugger. This
makes a call to a SQL 2000 database, and closes the connection, I then start
debugging after this point.
Someone has started to use a web application on a live sever which connects
to a SQL 2000 database, this database is a seperate server on a completly
different machine to the developing computer and DB.
However when I start debugging my application this live database hangs until
I stop debugging, does anyone have any idea why?
Many Thanks
PhilHi Phil
I tried following your post but it's a bit ambiguous, so I'm not 100% sure
what's exactly happening over there.. Anyhow, have you tried running the
"exec sp_who2" TSQL command to see if any connections are blocked whilst the
server appears hung? There are many scenarios where debugging can hang
applications, such as the application not draining cursors - perhaps your
application is doing that? Running sp_who2 will tell you if any connections
(spids) are blocked within the database engine. If youu find any blocked
connections, the next step is to analyse why the blocking connection is
hanging onto locks & fix that problem from there..
Regards,
Greg Linwood
SQL Server MVP
"Philip Poole" <philip@.dontreply.org> wrote in message
news:412628fb$0$193$db0fefd9@.news.zen.co.uk...
> Hello everyone,
> I have been debugging a module I have coded using the VS.NET debugger.
> This
> makes a call to a SQL 2000 database, and closes the connection, I then
> start
> debugging after this point.
> Someone has started to use a web application on a live sever which
> connects
> to a SQL 2000 database, this database is a seperate server on a completly
> different machine to the developing computer and DB.
> However when I start debugging my application this live database hangs
> until
> I stop debugging, does anyone have any idea why?
> Many Thanks
> Phil
>
>