Stairway to Server-side Tracing - Level 7: How to Automate SQL Traces using SQL Jobs
How to use SQL Jobs, scripts and SSIS to manage traces and trace data collection.
2019-03-26 (first published: 2012-01-18)
6,718 reads
How to use SQL Jobs, scripts and SSIS to manage traces and trace data collection.
2019-03-26 (first published: 2012-01-18)
6,718 reads
Level 8 of this stairway series looks at the automation of your tracing using Integration Services.
2019-03-26 (first published: 2012-09-03)
4,809 reads
In this level you will see how to employ the Data Collector feature of SQL Server to automate management of SQL Traces among multiple servers.
2019-03-26 (first published: 2012-10-24)
5,017 reads
I am responding late to a T-SQL Tuesday invite from John Sterrett. John’s call...
It’s been forgotten about and neglected for few years but I’ve decided to dust...
I am honored to announce that I have been renewed as a Microsoft MVP...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item People Make Odd Choices
Comments posted to this topic are about the item SQL Server 2022 Clusterless Distributed...
For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question: You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?
See possible answers