THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Allen White

SQL Server 2008 SMO Library Changes

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.


Published Saturday, October 18, 2008 1:35 PM by AllenMWhite



yazılım said:

Yep, i just came to the same error.

April 28, 2009 9:43 PM
New Comments to this post are disabled

About AllenMWhite

Allen White is a consultant and mentor for Upsearch Technology Services in Northeast Ohio. He has worked as a Database Administrator, Architect and Developer for over 30 years, supporting both the Sybase and Microsoft SQL Server platforms over that period.

This Blog


Privacy Statement