Can "exec sp_reset_connection" be removed from SQL Server Profiler trace data before running the tuning advisor?

Question

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?

Answer 1

Well, since no on has responded in a week's time, I'll at least post my experience. I recently successfully ran the Database Tuning Advisor on a bunch of Profiler trace data that excluded the "exec sp_reset_connection" and everything worked fine.