Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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?
I successfully ran the Database Tuning Advisor on a bunch of Profiler trace data that excluded the “exec sp_reset_connection” and everything worked fine. So, as far as I can tell, there don’t seem to be any negative side effects of excluding that data.