If you remember about SQL Server 2005 installation & feature documentation SQL-DMO has been referred as backward compatibility, and that feature will be removed in a future version of SQL Server. So the documentation has been heavy on users to avoid using this feature in new development work, and plan to modify applications that currently use this feature. Even you may have observed that within BOL publishing about DMO related information has been stopped.

The answer is use SMO, which is a collection of objects that are designed for programming all aspects of managing SQL Server. A new addition in the family is RMO - SQL Server Replication Management Objects (RMO) which is a collection of objects that encapsulates SQL Server replication management.

If you are familiar with SQL Native client programming and server side programming then SQL-DMO automates:

  • Repetitive or commonly performed SQL Server administrative tasks.
  • SQL Server object creation and administration.
  • Creation and administration of SQL Server Agent jobs, alerts, and operators.
  • SQL Server replication installation and configuration.

Similar to this SMO has many more features adding up the RMO programming too, you can search on BOL & MSDN documentation for your reference about features of SMO.

Coming back to subject matter, Joe Sack's blog post on SQL-DMO and SQL Server 2008 gave me a thought to remind you about actions that SQL programmers needed.

Take action now, than looking for workaround at later stages of your development!