A Tale of Partition Schemes and Disappearing Dragons
A tale in which is detailed how I used SWITCH PARTITION to efficiently load my data and save myself from the flaming jaws of death.
2017-10-20 (first published: 2015-11-02)
4,331 reads
A tale in which is detailed how I used SWITCH PARTITION to efficiently load my data and save myself from the flaming jaws of death.
2017-10-20 (first published: 2015-11-02)
4,331 reads
By Chris Yates
AI is no longer a niche capability – it is a leadership catalyst. As...
By Steve Jones
A friend was asking for help with some data analysis. This was in PowerBI,...
By Rohit Garg
The internet relies on IP (Internet Protocol) addresses to identify devices and route traffic....
Comments posted to this topic are about the item How a Legacy Logic Choked...
Hi i was surprised to see the approach my coworkers used to sunset talend...
Comments posted to this topic are about the item People Make Odd Choices
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