The SQL Server 2008 Datetimeoffset Data Type
The Datetimeoffset Data Type was introduced in SQL Server 2008 (and .Net Frameword 3.5) and is the most advanced date and time date type available.
2014-03-28 (first published: 2011-04-18)
16,943 reads
The Datetimeoffset Data Type was introduced in SQL Server 2008 (and .Net Frameword 3.5) and is the most advanced date and time date type available.
2014-03-28 (first published: 2011-04-18)
16,943 reads
This article shows how to implement low cost custom sequence numbering logic via a cunning use of the the ROW_NUMBER() function
2013-06-14 (first published: 2011-02-07)
20,091 reads
This article will show you how to automatically generate insert, update, and delete procedures for tables in your database
2013-01-01 (first published: 2011-02-10)
30,334 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