I want to find an alternate to the SQL profiler to trace-up the SQLBatch / Stored procedures that are ran against the database of SQL server 2008.
I have a problem where the client has an issue with an application. The issue happens randomly and is therefore very hard to trace.
I checked over the internet and found people saying a profiler or server-side trace should not be run for a long time and Extended Events should be used instead.
I have already looked at the extended events but these are fairly archaic and more performance-oriented than query-catching oriented. You may have a look at this thread for the information about it:
Is there anything else that could be use to trace-up the SQL_Batch_Completed events on SQL server without disrupting the performance on a production environment?