I have Visual Studio .Net project which uses ADO connection to call stored procedure of SQL Server database.
It is possible to set a breakpoing at stored procedure and debug it. I have local SQL Server and SQL Enterprise Edition installed.
I have Visual Studio .Net project which uses ADO connection to call stored procedure of SQL Server database.
It is possible to set a breakpoing at stored procedure and debug it. I have local SQL Server and SQL Enterprise Edition installed.
AFAIK, and if you are talking about an actual t-sql stored procedure, Your best bet will be:
There are a couple options i have heard of for debugging stored procs- eg: Direct Database Debugging.
here is a link from a good article i found explaining some of these: Stored Proc Debugging Methods
You can debug CLR procedures and functions from VS, see Debugging SQL
Transact-SQL is a different story, it needs special configuration steps and can be debugged from a special tool, see Using the Transact-SQL Debugger.
Use the SQL Server Profiler (under Tools menu in SQL Server Management Studio) to see the exact calls being sent from ADO to your database procedures. Then you can figure out where the problem is and start debugging, whether in SSMS or Visual Studio.