My local friendly DBA does not like the idea of allowing profiling on the SQL servers (even non-production ones) due to the impact on performance they have.
Ironically, I’m trying to reduce the need for a whole bunch of SQL queries, and would like to be able to check in a fairly non-invasive manner what queries are being sent over the wire, without impacting on the server performance. To this end is there a tool similar in approach to how useful Fiddler is for debugging HTTP connections, but allows client side profiling of SQL Server (at least for .net applications)? Or is it the case that running a profile for a single client will not impact on server performance?
You’ve tagged this ADO.NET. ADO.NET has inbuilt tracing facilities have you investigated those?
Are you on SQL Server 2008? If so how does your DBA feel about extended events? These can be configured to drop surplus events rather than cause server degradation as SQL Trace/ SQL Profiler does.
A light weight way of getting some idea of the queries that are being run and how often is
but that wouldn’t meet the specific client criteria though and is subject to the vagaries of plan caching.