You've installed SQL Server 2008 on a clean machine and your vb script that uses DMO doesn't work. You're asking yourself: What the heck happened? Did those goofballs over @ MS hose me? Deprecation of DMO was announced in SQL Server 2005, but SQL Server 2005 still installed DMO. In SQL Server 2008 we've taken the next step down the deprecation path - we ship DMO but don't automatically install it. There are two places to get DMO:
Generally it's best to go to http://www.microsoft.com/downloads, search for "SQL Server Feature Pack" and sort by Release Date to find the latest version.
With the addition of PowerShell support in SQL Server 2008 we highly encourage you to move off of DMO and start using SMO.
PingBack from http://hoursfunnywallpaper.cn/?p=3626
Thanks for the useful info. The installer for a product I'm testing against SQL2008 uses some DMO stuff to connect to the db, verify version number, create db for the product etc.. needless to say that didn't work too well until I turned on DMO
Thank you very much, I need DMO for integration to our backup sw.
Based on my findings the SQL Server 2012 production release does no longer support SQL-DMO.
It is not part of its Feature Pack either: www.microsoft.com/.../details.aspx