The Mysterious Case of the Missing Default Value
Sometimes things are not exactly how we think they are. Read the story of the missing default value and learn why.
2017-03-24 (first published: 2015-12-01)
6,881 reads
Sometimes things are not exactly how we think they are. Read the story of the missing default value and learn why.
2017-03-24 (first published: 2015-12-01)
6,881 reads
Database ownership is an old topic for SQL Server pro's. Check this simple lab to learn the risks your databases can be exposed to.
2015-01-29
10,971 reads
2013-11-15
2,002 reads
2013-09-23
2,341 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...
I have tried a number of times to export and then import my SSMS...
Hi I need to connect to a SQL server via FQDN - that is...
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