Q:

SQL Server Profiler - Textdata On 'Prepare SQL' and 'EXEC Prepared SQL' Commands Blank

I have inherited an application that uses SQL Server as it's database.
To understand the tables accessed from the application when doing specific tasks in the closed code application I usually use SQL Profiler to identify the table and queries performed behind the scenes for each function ( for example adding a customer ).
However with this application all the SQL statements issued are 'Prepare SQL' and 'Exec Prepared SQL' both of which on this application return nothing in the 'TextData' column which usually shows the SQL commands performed.
The login events are also not shown and all SQL statements are shown in profiler attributable to the applications service account.   I have therefore deduced users sign on to the application but the application communicates with the database via the service account and the SQL statements are hidden somehow.
Does anybody know how to expose/reveal the TextData column contents on the 'Prepare SQl' and 'Exec Prepared SQL' statements so I can see which tables the application is using?   I know there are lots of packages out there that claim they can do this but I suspect they are just using the same information as profiler so won't show anything extra.

A:

Select the SQL:StmtStarting under TSQL and SP:stmtStarting under Stored Procedures in Event Selection tab of the Trace properties.
This way you can make you don't miss any statements in the Text Data.

