The Bit Bucket

A few months ago, I was asked a question by a friend of mine who is also a Data Platform MVP. He was trying to express a query like this:

SELECT si.StockItemID, si.StockItemName, si.Size, si.LeadTimeDays FROM Warehouse.StockItems AS si WHERE (si.Size, si.LeadTimeDays) IN (('M', 7), ('XXL', 7), ('XXL', 12));

He was trying to select stock items where the combinations of Size and LeadTimeDays are in the list. Unfortunately, in SQL Server and T-SQL, an IN can only be used with a single column. We can’t use a row constructor like (si.Size, si.LeadTimeDays) as a lookup into a list of constructed rows.

2019-06-13

I often need to know if a date that I’m working with is a week day or a weekend. While T-SQL has some functions that help with that, you need to use a combination of them to get a reliable outcome that’s independent of the current session settings. (Based on Saturday / Sunday being weekends but easy for you to change if you have different weekends). To make it easy, we added two functions IsWeekday and IsWeekend to our free SDU Tools for developers and DBAs.

2019-06-12

For better or worse, I spend a lot of time in hotels, airline flights, dealing with many suppliers, etc. What’s become really common now, is that a few days later, they’re sending me a survey asking me how they did.

Now I’m sure that they’re just trying to follow some best practice to make sure they’re delivering what was expected, but lately, I’m finding many of the surveys really quite annoying. I’d like to suggest some simple rules to avoid that.

2019-06-11

We use comparison operators in T-SQL expressions. And the expressions are often used in WHERE clauses. For example:

WHERE CreditLimit = 10000

The = (equals) sign shown is a simple one but T-SQL has a number of operators.

Most people writing T-SQL code are familiar with these:

= Equals <> Does not equal < Less than > Greater than <= Less than or equals >= Greater than or equals

However, less people seem to be aware of the other operators added a while back:

2019-06-10

I was working in a bank a few weeks back. They were planning an upgrade from SQL Server 2008 R2 to SQL Server 2017. One of the things that I raised with them is why there were extended stored procedures that had been added to the master database. And they told me they were the result of a penetration test.

OK, so this had me intrigued.

The logic that was being applied was that the penetration testers required the bank to have SQL CLR disabled. No-one in the bank could tell me why; just that it was required to be off.

2019-06-06

Many of my friends have told me that they like how concise the PIVOT and UNPIVOT operators are, but they find the syntax confusing. I must admit that I wasn’t a big fan of these when they were added in SQL Server 2008 as they didn’t really add anything to the language that I couldn’t have done with CASE statements, etc. and there were so many other parts of the language that needed work.

2019-06-05

In a previous post, I discussed the way that adjectives have been replacing adverbs, and pondered about what had happened to “ly”. For example:

Drive Safe

rather than:

Drive Safely

I had quite a bit of feedback on this, both on and offline. Language discussions are always busy. But another similar trend came up in a discussion that I recently took part in.

A friend asked that if you used the term:

2019-06-04

I showed earlier how we can retrieve data from a table using a SELECT clause. It can also be used to determine which columns are returned, and which table the data is being retrieved from. But we don’t always want all the rows to be returned. The WHERE clause fixes that.

It’s important to understand that the WHERE clause limits the rows returned to ones where the expression in the WHERE clause evaluates to a logical TRUE value.

2019-06-03

A while back I purchased a number of Audible titles, thinking I’d listen to them as I traveled around. I grabbed a number of ones related to presentation and I thought I’d also check out some general self-improvement titles.

What I didn’t realize, is although they had different titles, I’d basically bought a number of copies of essentially the same book, but with different titles. This was one of them.

2019-05-31

This is part 7 in a series of posts:

• Part 1 covered being sure there is a locking and blocking issue
• Part 2 covered the impact of RCSI
• Part 3 looked at the impacts of indexing on locking and blocking
• Part 4 looked at what deadlocks really are and how SQL Server handles them
• Part 5 looked at how applications should handle deadlocks
• Part 6 looked at how to avoid deadlocks in the first place

Today, though, I want to look at how to handle deadlocks if you must do that in T-SQL.

2019-05-30