SQL Server Workarounds

360 Questions

We’ve been asking you folks a lot about what you’d add to SQL Server, and we’ve gotten some great answers. There are even some that have been answered in the last couple versions of SQL Server.

For instance, 2016 brought us STRING_SPLIT!

SQL Server 2017 has a whole bunch of neat stuff:

And while I’m thrilled with the new functionality (haw haw haw), there’s still a lot of stuff other platforms can do that we need weird workarounds for. I started thinking about this while answering a question on Stack Exchange about how SQL Server users mimic the greatest and least functionality available in other products.


As SQL Server developers, what weird workarounds do you have to implement due to missing functionality?

Here’s the thing: I don’t want you to leave a bunch of gripes and code in the comments. Comments like that are hard to read and search and typically don’t help other people out.

Rather than do that, I want you to do something more beneficial for everyone (yourself included)

After you do that, head back here and post a link to wherever you chose to do your business. I’ll do a roundup of all the best ones and add them to the post.

Thanks for reading!

Previous Post
Paste The Plan…Now With Comments
Next Post
French makes everything sound so sexy.

14 Comments. Leave new

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.