Bugs on Andy M Mallon - AM²

When STRING_SPLIT() falls short

Fri, 20 Mar 2020 10:00:54 -0400

Aaron attempting a STONE_SPLIT at a recent curling competition. This morning, my friend Aaron Bertrand (blog|twitter) posted a plea for help with STRING_SPLIT() improvements. I'm very much in Aaron's corner on this, having written about the olden days myself.

Why `STRING_SPLIT()` is supposed to be awesome

CLR was fast, but inaccessible to many DBAs. XML was almost as good, but ugh, XML. And multi-statement table valued functions are evil but prevalent.

STRING_SPLIT() promised to be both super fast, and lift the code maintenance problem for DBAs who don’t know .NET and struggle with the crazy XML syntax.

Deadlock when creating a database - A Query Store bug

Tue, 20 Mar 2018 09:00:17 -0400

Earlier tonight, I sat down to install Reporting Services on my laptop. I haven’t played with SSRS 2017 yet, so I figured I’d poke around some. Much to my surprise, the configuration failed when creating the ReportServer database, reporting a deadlock. When I looked at the database instance, I found the ReportServer database there, but with no objects it in, and the ReportServerTempDB database missing.

Configuring Replication with Availability Groups

Fri, 23 Feb 2018 10:00:41 -0500

I fancy myself more of a Jedi, but I appreciate the Empire's dedication to replication

I’ve used replication and Availability Groups together before. Replication works great with an AG as both a publisher or a subscriber (though, not as a distributor–you can’t add the distribution database to an AG). I was surprised when I recently ran into a problem configuring replication on a database that was in an AG.

DROP TABLE Bug on Filestream Garbage Collection

Tue, 08 Dec 2015 15:36:05 -0500

FILESTREAM is not a particularly popular feature of SQL Server–if you’re using it, you are in the minority. If you have a database with filestream in an Availability Group, then you’re REALLY in the minority. At my 9-5, this is being done, and it’s apparent that this combination of features isn’t a robust combination.

Really Long Descriptions on SQL Agent Jobs

Fri, 25 Sep 2015 14:38:00 -0400

WARNING: Silent truncation ahead

Have you ever tried to enter a really long description on a SQL Agent job?

Maybe you were trying to put some sort of warning to people who might be trying to edit the job, or triage info for when the job fails. (Ok, so this sort of documentation should be on your wiki, not in a job description… but stuff happens)