Most of the time, we want SQL Server T-SQL queries to run as fast as possible, just the same as we want programs in any programming language to run as fast as possible.
But there are times when you want SQL Server to just sleep for a while, and without tying up system resources (like spinning around on the CPU).
Example of this would be waiting for new entries in Service Broker queues, or waiting to retry deadlocks.
2017-11-10
This is a really popular shortcut in SQL Server Management Studio (SSMS) but I continue to be amazed how many people aren’t aware of it.
Object Explorer is a very useful part of SSMS and you can drag pretty much any name that you see in it, across to a query window.
You could do the same for each column in the Columns list.
You might also realize that you can hover over the asterisk and see a list of columns:
2017-11-09
I love it when SQL Server gets brand new T-SQL language features.
SQL Server 2017 added a great new language feature called TRANSLATE. It’s been in some other products like Oracle for a while but it’s just been added to SQL Server.
Imagine I have a string like this:
’[02] 9992:2343’
But what I really want is one like this:
’(02) 9992-2343’
Up to SQL Server 2016, I could do this with a series of replace statements:
2017-11-08
Many people know that I have an issue with ORMs (object relational mappers). It’s worth spending a blog post to describe why.
Unfortunately, I spend my life on the back end of trying to deal with the messes involved. The following are the key issues that I see:
Potentially horrid performance
I’ve been on the back end of this all the time. There are several reasons. One is that the frameworks generate horrid code to start with, the second is that they are typically quite resistant to improvement, the third is that they tend to encourage processing with far too much data movement.
2017-11-07
I’m not a great fan of linked servers in SQL Server but they are often necessary. I really wish the on-premises product supported External Data Sources and External Tables. But in the meantime, what I see all the time, is people hardcoding server names like this:
SDUPROD2016.WWIDB.Payroll.Employees
That makes your code really hard to manage. One option to get around that is to use synonyms.
Instead of sprinkling references to that table all through the code, you can create a synonym for it like this:
2017-11-06
Occasionally I run into a need to clear out all objects in a schema in a SQL Server database. Sometimes it’s because I want to remove the schema itself. It’s often painful to do as I have to find all the types of T-SQL objects, and then often have to remove them in a particular order.
So I added a tool to my SDU Tools collection to do just that.
2017-11-03
The on-premises versions of SQL Server have the ability to connect one server to another via a mechanism called Linked Servers.
Azure-based SQL Server databases can communicate with each other by a mechanism called External Tables. I’ll write more about External Tables soon.
With Linked Servers though, I often hear people describing performance problems and yet there’s a configuration setting that commonly causes this. In Object Explorer below, you can see I have a Linked Server called PARTNER.
2017-11-02
SQL Server Management Studio (SSMS) is a wonderful tool but there are so many ways built-in shortcuts that many users don’t seem to be aware of.
A simple example, is if I want to script all the indexes on a table (or all the tables, all the stored procedures, etc, etc.). Yes you can do that the long way by using the Generate Scripts option but there’s a better way.
2017-11-01
I recently shipped the latest update to my SDU Tools collection.
This time I decided to add a tool that’s in the “cute” category. It’s called InvertString and you can see it action in the image above.
Yes, it takes an input string and returns a string that looks quite like an upside down version of the same string.
As part of the inversion I also reversed the order of the string so when you look at it upside down, it still looks correct. But if what you really want is a mirror image, you could combine it with REVERSE to achieve that outcome:
2017-10-31
Most SQL Server developers are aware that they can create computed columns. We do that by defining a column AS some expression like this:
Each time the value from that column is queried, the calculation is performed so the result can be returned. This makes sense when the value is changing regularly and the value is queried infrequently.
However, according to my completely subjective statistics, most computed columns are queried much more than they are ever changed. So why work the value out each and every time?
2017-10-30
