Using Comments to Quickly Test CTEs
A quick tip for using a combination of block and line comments to test CTEs
2014-11-10
7,430 reads
Carl P. Anderson
Concatenating Rows
Often in database design we store different values in rows to take advantage of a normalized design. However many times we need to combine multiple rows of data into one row for a report of some sort. New author Carl P. Anderson brings us some interesting T-SQL code to accomplish this.
2011-03-04 (first published: 2009-10-14)
150,341 reads
Blogs
What is KTLO? Keep The Lights On vs Project Work in Agile
By Rohit Garg
🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...
The PASS Summit on Tour in Dallas
By Steve Jones
The PASS Summit goes on tour this year, with a September stop in Dallas....
SQL Server Auto-settings: The Good, the Bad, and the Ugly
By Kevin3NF
Settings That Could Be Hurting Your Performance If you’ve ever created a new SQL...
Forums
How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory
Comments posted to this topic are about the item How a Legacy Logic Choked...
Formatting Dates and Times: The SQL Dialect Divide
Comments posted to this topic are about the item Formatting Dates and Times: The...
Query Plan Regressions --
Comments posted to this topic are about the item Query Plan Regressions --
Question of the Day
Query Plan Regressions --
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