title: Can "exec sp_reset_connection" be removed from SQL Server Profiler trace data before running the tuning advisor?
body: <p>Based on information I have read about the "exec sp_reset_connection" which appears in SQL Server Profiler trace data when connection pooling exists, it seems safe--or logical, rather--to remove/exclude it from trace data to be considered by the Database Tuning Advisor. Any thoughts or objections?</p>