While preparing for a presentation at PASS next month I tested my PowerShell script to back up user databases on a server. This script has been running flawlessly against SQL Server 2005 for a couple of years, so I was really surprised when PowerShell returned a screen full of errors and no backups.
What slipped my mind was something I'd reported a year ago here, that a number of objects have been moved from the SMO dll to the SMOExtended dll.
The problem was easily resolved by adding the following line to the top of my PowerShell script:
[System.Reflection.Assembly]::LoadWithPartialName('Microsoft.SqlServer.SmoExtended') | out-null
Fortunately it's a minor gotcha, but one that can cause some problems after an upgrade if you're not prepared.