Determine Stored Proc from ASP.NET
Hi All,
I'm trying to do some reporting on a 3rd party application.
I have admin access to the front end and SA for the backend.
The application dumps some data to a CSV, which our users manually use to crunch numbers in different ways . . . I'm trying to automate that process to reduce the errors and time.
My issue is the web app is pre-compiled. It looks like the application has a default page, which then takes a query string of a pageID to load the page from the database.
All of that to say that I'm trying to find out what stored procedure / query is being run against the DB to generate the data.
The applicaiton is quite large (a few hundred stored procs) with a number of tables and trying to parse out the information in a meaningful way is going to be a pain, so trying to short cut it. Getting help from the vendor is NOT possible.
I thought of SP_who2 . . . but that doesn't give me the info I need. DB and front end are on different boxes.
Any thoughts on how about going to extract the stored proc / query from a dynamically loaded page?
I'm trying to do some reporting on a 3rd party application.
I have admin access to the front end and SA for the backend.
The application dumps some data to a CSV, which our users manually use to crunch numbers in different ways . . . I'm trying to automate that process to reduce the errors and time.
My issue is the web app is pre-compiled. It looks like the application has a default page, which then takes a query string of a pageID to load the page from the database.
All of that to say that I'm trying to find out what stored procedure / query is being run against the DB to generate the data.
The applicaiton is quite large (a few hundred stored procs) with a number of tables and trying to parse out the information in a meaningful way is going to be a pain, so trying to short cut it. Getting help from the vendor is NOT possible.
I thought of SP_who2 . . . but that doesn't give me the info I need. DB and front end are on different boxes.
Any thoughts on how about going to extract the stored proc / query from a dynamically loaded page?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No real perfromance impacts when running the profiler. The only thing to watch out for is it writes to the C Drive when saving the data, so that can be problematic (in my case I only had 1.7 GB free . . . 12GB System partition) as I ran out of space. Clearing the trace window will free up the space.
Thanks for the help.
Thanks for the help.
ASKER
I'll check it out. This would be on production and forget if profiler has a performance impact.
Are there any risks?
Sorry for the late reply. We got another project dumped on us that needs to be done ASAP. Responses may be a bit slow but will get to this soon.