Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a SqlDataSource that calls a stored proc. When the page loads a Gridview loads that uses that SqlDataSource.
At this time I want to be able to debug the stored proc.
I DON’T want to debug the stored proc on it’s own.
I want to see what values are actually being passed to the stored proc and what it is actually doing.
Use Sql Server Profiler. You can listen all requests to your sql server if you have rights.
ADDED:
“SQL Profiler without sysadmin rights” or “this one” can help you.
Test your code on your own sql server(with sa rights), not production. If it works at your one it will work on production. Otherwise demand Trace rights to do to your job!
So, use a local server (express edition for example, or developer edition) with ALTER TRACE or sysadmin rights to use SQL Server Profiler. Don’t use table and don’t change your stored procedure. Profiler traces all calls to the sql server with param values. Just catch this calls!
ADDED:
I have found ADO.NET Trace Logging. I think, this is what you are looking for. On my opinion this tracer is not so good to use, but in your case, I think it can help.