2010-09-29
3,142 reads
2010-09-29
3,142 reads
2010-06-28
3,483 reads
2010-05-31
3,575 reads
2010-04-20
4,595 reads
2010-03-17 (first published: 2010-03-04)
1,524 reads
This article will demonstrate an efficient way to reuse gaps in an identity column. Please note that this is something you normally shouldn't be bothered about in a well-designed database or application. However, there are circumstances where you are forced to do this.
2010-03-03
2,989 reads
Learn a foolproof way to get identity values for multi-row inserts with the OUTPUT clause in SQL Server 2005 without using a cursor.
2010-01-20
4,564 reads
2010-01-04
4,200 reads
2009-10-09
5,321 reads
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...
By Rohit Garg
🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...
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