With origins from the world of “Submarine ‘Dolphin’ Qualification” questions, an “Oolie” is a difficult question to answer, or the knowledge or fact needed to answer such a question, that may or may not pertain to one's duties but tests one's knowledge of a system or process to the limit. Introduction Contrary to what many […]
2019-08-08
6,282 reads
Understanding indexes and how they work can be complicated enough for a Jr. DBA, but throw in all the different options and properties and an index can soon be overwhelming. Brady Upton takes an introductory look at creating an index in SQL Server using SQL Server Management Studio. He explains what each index property is meant for and the various options presented.
2013-11-19
4,619 reads
By Steve Jones
A friend was asking for help with some data analysis. This was in PowerBI,...
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...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item People Make Odd Choices
Comments posted to this topic are about the item SQL Server 2022 Clusterless Distributed...
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