The OUTPUT clause
One of the features that I have been using quite a lot lately is the OUTPUT clause.
This clause can be...
2011-01-09
928 reads
One of the features that I have been using quite a lot lately is the OUTPUT clause.
This clause can be...
2011-01-09
928 reads
Recently I set up replication and as the target server was not on our domain I initially used an IP...
2010-09-20
975 reads
Ever wondered what happened to the SQL 2005 Surface Area Configuration Utility in SQL SERVER 2008.
Well you can accomplish pretty...
2010-09-14
870 reads
G'day,
This is pretty much my first blog post - at least on sqlservercentral.com - so to get started I thought that I'd...
2010-09-01
435 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