This stored procedure was written to complement the automated profiler trace create procedure (should be here somewhere - check the scripts).Bascially, given the database (sample script to create the database included, but you may want to personalize it), this stored procedure will import the tracefile content into the table, which is indexed on expected search […]
2005-10-03 (first published: 2005-03-04)
362 reads
This stored procedure is created to be invoked (in my case by SQL Server scheduled job), and will then create a tracefile to a specified file location (ensure that if this is NOT local, your SQL Server Agent runs on a domain account that has access to that drive. The Stored procedure will create files […]
2005-03-16 (first published: 2005-03-04)
437 reads
By Rohit Garg
🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...
By Steve Jones
The PASS Summit goes on tour this year, with a September stop in Dallas....
By Kevin3NF
Settings That Could Be Hurting Your Performance If you’ve ever created a new SQL...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item Formatting Dates and Times: The...
Comments posted to this topic are about the item Query Plan Regressions --
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