Can I remove "exec sp_reset_connection" from SQL Server Profiler trace data before starting the configuration consultant?

Based on the information I read about "exec sp_reset_connection" that appears in SQL Server Profiler trace data when there is a connection pool, it seems safe - or logical - to remove / exclude it from the trace data that will be considered by the database configuration adviser. Any thoughts or objections?

+4
source share
3 answers

I successfully launched the Database Setup Advisor on the Profiler trace data bundle, which excluded "exec sp_reset_connection", and everything worked fine. So, as far as I can tell, there are no negative side effects to exclude this data.

-1
source

Column filters set TextData Not Like exec sp_reset_connection

+15
source

If you want to use ADO.NET connection pooling , the answer is: Absolutely not!

0
source

All Articles