I was excited to learn this week that I’ve been chosen as a participant in the Friends of Red Gate program for 2015. For those of you who are not SQL folk, you can stop reading now – Red Gate is a company who makes top-shelf products for working with SQL Server.

This should be quite an interesting experience, as we’ve recently started heavily leveraging some of the Red Gate products in our efforts to provide continuous deployments. I hope to not only gain from this myself, but to also give back in some meaningful way, based on our day-to-day use of the tools.

Red Gate has done, and continues to do, great things for the SQL Server community. I’m pleased to be in a position to help those efforts, and to possibly return the favor in some small way.

Thank you, Red Gate!


Most of my peers, and likely yours as well, work in some sort of technical field. Odds are that they’re proficient readers who can digest the driest of technical material. They’re probably good with math, and a large portion of them are likely science geeks. How many of them can write? I’m not talking about writing their name on their homework, I’m talking about writing clear, concise emails, or meeting agendas, or technical documentation. I’ll bet most of them stink at writing, and that’s wasting money, wasting time, and possibly hurting their paycheck.


New version of sp_BackupDatabases released this morning, first update that I’ve made available in a while. I’ve been running this version myself for months, so it’s well-tested, I just forgot to post the update here.

Changes in this version:

– Include brackets around database name in all commands, in case someone uses a reserved word, or a space, or something equally stupid in a database name
– Add parameter @output_log_directory parameter to define location of job output logs. If not specified, will use default SQL log directory
– Sub-jobs now inherit notification properties of parent job
– Expand “frequency” parameters to 4 characters to allow for larger hourly intervals, e.g. “168H”
– Add “fail-safe” schedule to each sub-job to run on SQL startup, to prevent “stuck” jobs resulting from a server restart

Grab this latest version, or any of the previous versions, from the sp_BackupDatabases download page: