A Fine Slice Of SQL Server
Shane O’Neill dives right into the deep end:
I once had the annoyingly complex T-SQL to change MS format time into a human-readable format memorised.
To be specific, that’s the nasty integer format used in SQL Agent jobs, a format which hasn’t made sense to use in decades (if it ever did).
Leave a CommentAndy Yun shows off some random skills:
First, there are times where you need multiple random numbers. Simply using multiple iterations of RAND() in a single statement won’t cut it, as you need to vary the seed. So I keep this snippet handy for when I need a bunch of random values in a single statement:
Click through for that as well as two more uses of RANDOM(). This is my reminder that RANDOM() generates data across a uniform distribution (every value in the range is equally likely to be chosen), making it great for these sorts of experiments but can look weird by itself if you’d expect non-uniform distributions of the data. For that, you would need some distributional trickery—though frankly, between the uniform and normal distributions, you’ve probably covered about 95-99% of test dataset needs.
Kevin Chant has a two-fer for us:
My first personal go-to script is one that has helped me out a lot over the years. Because I have used it a lot to identify missing indexes. I know there are a few different versions available online that you can use. However, I tend to use the one that comes with Glenn Berry’s Diagnostic Queries.
It is so easy to use. I’m not sharing the snippet of code on here because I want to encourage people to download the entire diagnostic script instead. Just download the script that is relevant for your version of SQL Server and search for ‘Missing indexes’.
Read the whole thing.
Leave a CommentChad Baldwin goes the extra mile:
I’m excited that this will be my first time participating in a T-SQL Tuesday topic!
Most of my time is spent writing T-SQL, PowerShell and working in the PowerShell terminal, so that’s how I’ll split the post up.
I had to cut it short otherwise this post would be a mile long. If you’re interested in seeing more quick tricks, SQL Prompt snippets, etc, please leave a comment and let me know and I can do a Part 2 in the future.
Click through for a baker’s dozen plus a couple spares.
1 CommentDeborah Melkin does not take kindly to bugs:
I often find that I have to write complicated stored procedures where I need to check things as I go along. My go-to for using this snippet is when I write stored procedures that use dynamic SQL. You’d be surprised (or not) at how often I have had to do this over the years. There’s been functionality where the user gets to choose the columns being used, rewriting ORM data layer “catch-all” queries to improve performance, and cross database queries where the name of the database may not be the standard name (think development and QA databases living on the same SQL instance.)
Click through for an example of where the @Debug parameter pays off. My recollection was that, for really long NVARCHAR(MAX) strings, running PRINT by itself might cut off the code after ~4000 characters, but that could be a historical recollection.
Deepthi Goguri re-shares some helpful scripts:
For the past couple of years as a DBA, I migrated several databases and used many handy scripts that helped me made my work easier. These scripts may be simple but if you have a migration project involving several SQL Servers with some hundreds of databases, test and production database migrations becomes tedious. I would like to share some of then here which you might already known them very well.
Click through for three scripts.
Leave a CommentChad Callihan has a few close-to-one-liners:
The most common, short script I could think of may very well be one of the shortest T-SQL scripts that can be executed. When you want to know what version of SQL Server you are connected to, you can run this script:
Read on for that one-liner as well as a few other short scripts.
Leave a CommentMala Mahadevan has a few short-ish Query Store scripts for us:
I use Query Store a lot where I work – and I’d like to share queries I use on Query Store DMVs that I find incredibly useful.
My favorite is one below, which I use to see stored procedure duration. It comes with other information including plan id, start and end time – all of us help me see red flags right away if there is any query not performing as well as it should.
Click through for that script as well as two more.
Leave a CommentAndy Mallon wants a database all of his own:
I’ve written about my DBA Database quite a few times. Some of the code in that database is written recently, and some of it was originally written a decade ago. Regardless of how old it is, or how good of a DBA I was when I wrote it, these little scripts are life-savers, and they are always at my fingertips.
And Andy has made them available to your fingertips as well. And the rest of your hands, I suppose.
Leave a CommentRob Farley has a quick script to find references in SQL Server:
As a consultant, the kind of work that I do from customer to customer can change a bit. Sometimes I’m reviewing people’s environments; sometimes I’m performance tuning; sometimes I’m developing code or reports or cubes; sometimes I’m writing T-SQL, but it’s often DAX or PowerShell.
Click through for a quick script to search modules for a particular string.
Leave a Comment