February 20, 2013 at 11:08 am
Hi,
Is there a way to do client-side tracing of the SQL commands being sent from a client box to a SQL Server server without using the SQL Profiler or the sp_trace* stored procedures?
I have a packaged application that is poorly documented and has poor reporting capabilities. I need to write queries against the database tables, in some cases without knowing what tables I'm even dealing with. The outsourced IT company managing our servers has been uncooperative with my requests for access to either the SQL Profiler or the underlying stored procedures.
I'd like to be able to capture the SQL passing from the client app to the server when I perform a function in the app in order to jump-start the process of identifying the table(s) involved in the particular form I'm working in. Once I know the tables and a bit of the SQL, I would be better positioned to write my own customized versions of the queries.
Can this be done?
Thanks for any help you can give.
Wayne
February 20, 2013 at 12:35 pm
Is the client app using the SQL Server Native Client? If so you might be able to trace activity that way:
I am not sure if the same tracing capabilities were available in the 2005 native client but it might be worth a look.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
February 20, 2013 at 1:29 pm
wayne_dyck (2/20/2013)
Hi,The outsourced IT company managing our servers has been uncooperative with my requests for access to either the SQL Profiler or the underlying stored procedures.
Run SQL Profiler against your dev server or your local box.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply