Hi Nabil,

Here a checklist of different settings to make:

1) Enable debugging for your project. Right click on the "Project" in the
Solution Explorer and choose properties. Next (on the left pane), click on
Configuration Properties|Debugging and check "SQL Server debugging"
2) Make sure that you have execute permission on the SQL Server stored
procedure: master.sp_sdidebug. See note below.
3) Open the SP using the Server Explorer and click on the margin to set a
breakpoint location.
4) Try to debug the SP using the Server Explorer (Step Into Stored
Procedure). If this works, you should be able to debug it from your
application. If this does not work, proceed to step 5.

The online help says:
To give debugging access to a SQL Server user, you must give the user
permission to execute the extended stored procedure sp_sdidebug. Use the
Enterprise Manager shipped with SQL Server or consult your database
administrator.
For Windows NT 4.0 only, you must perform the following steps.

To set up SQL Server for debugging for Windows NT 4.0

1.. From the Start menu, choose Settings and click Control Panel.
2.. In Control Panel, choose Services.
3.. Select MSSQLServer and then choose Startup.
4.. Check the Log On As settings. If the option is set to System Account,
change it to This Account, enter the valid domain and user account (in the
form domain\account) of a user with administration privileges, and then
enter the password.
5.. If you have changed the setting, restart SQL Server.
See "Setting up SQL Debugging" which lists all of the requirements.


>After adding a debug breakpoint on SQL strored procedure, I'm getting the following message "The breakpoint will not currently be hit. No symbols have been loaded for this document"
>
>How can I debug SQL stored procedure?