Catching SQL Server System Object Changes
Let's say you get your hands on a brand new version of SQL Server that you haven't played with before, and you want to know what system objects have changed - DMVs, DMFs, system stored procs, yadda yadda yadda. Sure, you could read the documentation - but ain't nobody got time for that, and they're probably leaving out the juicy stuff, right? Here's what I do (thanks to improvement suggestions from Kendra):