SQL Server 2017 – Deferred Name Resolution Bug.

This issue came up recently while in the midst of an upgrade to SQL Server 2017, but it's actually not related to the upgrade and has been around all along on previous versions. So I took a moment to write this, cause a friend told me it would make a nice blog post. Mad credit…

Select and Start a SQL Job without knowing the full job name or history

So I was trying to figure out how to get the TLog backup job's name based on Back History because in this case, the job name happens to vary between SQL Server Instances. Sounds simple enough (well...not quite), then I realized for new SQL Server instances this job might not have even ever ran...so there went…