Unexpected View Performance
Views that use implicit conversion to return result sets may use a different query plan than the statement executed in query analyzer.
2014-04-18 (first published: 2011-01-11)
13,872 reads
Views that use implicit conversion to return result sets may use a different query plan than the statement executed in query analyzer.
2014-04-18 (first published: 2011-01-11)
13,872 reads
Complete package to allow tracking of any data that Profiler can capture and storage for auditing purposes, use to satisfy SOX compliance.
2009-07-16
5,871 reads
Working with filegroups and managing the location of your various objects can be a cumbersome task in SQL Server. New author Thom Bolin brings us a technique and some code that worked well for one of his clients.
2008-09-15
6,227 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 Navigating Multi Platform Realities in...
I have tried a number of times to export and then import my SSMS...
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