When your application closes its data connection, the connection to the computer that's running SQL Server might not be completely closed. If the connection-pooling feature is enabled, the connection is held in a pool so that the connection can be reused if the application tries to reopen the connection later. However, when a connection is re-established through connection pooling, SQL debugging isn't re-enabled. If you enable the connection-pooling feature for the SQL Server database connection that your application uses and your application uses a reopened connection from the connection pool, you might not be able to debug a SQL Server stored procedure more than one time from the native code or from the managed .NET Framework code. To find out how to work around this problem, read the Microsoft article "You cannot debug a SQL Server stored procedure more than one time while debugging managed .NET Framework code in Visual Studio .NET" at<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

   http://support.microsoft.com/?kbid=837221