NLB drainstop command issues

Hello,

We use the NLB drainstop command to gracefully move connections from one database server (server A) to another (server B) but we discovered with one application in particular that the connections stay alive on the server A.

The applications make DB connections using standard .NET System.Data classes.

Has anyone experienced this before? Any pointers on what to check for?

Thanks

Alexwhich database is this?

you have posted in the non-database-specific "database concepts" forum, and it sounds like this thread should be moved to a database-specific forum|||Thanks. I'll post it in the sql server forum.|||Hello,

We use the NLB drainstop command to gracefully move connections from one database server (server A) to another (server B) but we discovered with one application in particular that the connections stay alive on the server A.

The applications make DB connections using standard .NET System.Data classes.
The database servers are SQL Server 2005.

Has anyone experienced this before? Any pointers on what to check for?

Thanks

Alex|||no, don't do that, we'll just move this thread over there

:)|||no, don't do that, we'll just move this thread over there

:)Hehe!! :) Thank you sir!

I hope someone here can assist!