 <p>Great Question! If I'm not mistaken I don't think debugging is possible inside of SQL Management Studio anymore (as it was back in the SQL Server 2000, Enterprise Studio days).</p> <h2>Instructions to Remote Debug MS SQL Stored Procedures within Visual Studio 2005</h2> <ol> <li>Launch Visual Studio (If you're running from Vista, <strong>Run As Administrator</strong>)</li> <li>Within Visual Studio 2005 click <strong>View->Server Explorer</strong>, which you'll notice brings up a panel with a <strong>Data Connections</strong> element.</li> <li>Right click on <strong>Data Connections</strong> and select <strong>Add Connection</strong></li> <li>Ensure the <strong>Data Source</strong> is set to <strong>SqlClient</strong>.</li> <li>Fill out the Server connection information, filling in the database name where the stored procedure that you wish to debug lives.</li> <li>Once a successful connection is made you'll notice the a tree for the database is populated that gives you the list of Tables, Views, Stored Procedures, Functions, etc.</li> <li>Expand <strong>Stored Procedures</strong>, finding the one you wish to debug and right click on it and select <strong>Step Into Stored Procedure</strong>. </li> <li>If the stored procedure has parameters a dialog will come up and you can specify what those parameters are.</li> <li>At this point, depending on your firewall settings and what not, you maybe be prompted to make modifications to your firewall to allow for the necessary ports to be opened up. However, Visual Studio seems to handle this for you.</li> <li>Once completed, Visual Studio should place you at the beginning of the stored procedure so you can starting the act of debugging!</li> </ol> <p>Happy Debugging!</p>