Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All
Important This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.

Remote Transact-SQL Debugging on Windows Vista

This topic applies to:


Visual Basic



Web Developer


Topic does not applyTopic does not applyTopic does not applyTopic does not apply


Topic does not applyTopic does not applyTopic does not applyTopic does not apply

Pro and Team

Topic appliesTopic appliesTopic appliesTopic does not apply

Table legend:

Topic applies


Topic does not apply

Does not apply

Topic applies but command hidden by default

Command or commands hidden by default.

When you do T-SQL debugging or T-SQL application debugging against a remote SQL server, Visual Studio must configure the Windows Firewall before remote debugging can begin. Normally, this configuration occurs when you try to step into a T-SQL stored procedure on a remote computer.

On Windows XP, the Windows Firewall configuration starts automatically. On Windows Vista, the new security model requires that you grant permission before the software can configure the Firewall. As a result, a Visual Studio dialog box appears, informing you that the Firewall has to be configured, followed by the Windows Vista User Access Control dialog box. If you grant permission in the UAC dialog box, the Configure Firewall for Remote Debugging wizard appears.

Community Additions

© 2015 Microsoft