Edit

Backward Compatibility in SMO

  • Article

Applies to: SQL Server Azure SQL Database Azure SQL Managed Instance Azure Synapse Analytics

SMO applications that were written using previous versions of SQL Server can be recompiled by using SMO in newer versions.

Migrating SMO Applications

References to SMO DLLs in older versions of SQL Server must be removed, and references to the new SMO DLLs that are provided with newer versions of SQL Server must be included.

Minimally, you would reference the following:

  • Microsoft.SqlServer.ConnectionInfo

  • Microsoft.SqlServer.Smo

  • Microsoft.SqlServer.Management.Sdk.Sfc

These files are required for connection classes, SMO utility classes, and foundation classes.

Note

SmoEnum.dll has been removed so references to it must be removed from the SMO project.

The namespaces have also changed, so you can use the following:

For Visual C#
using Microsoft.SqlServer.Management.Smo;  
using Microsoft.SqlServer.Management.Common;
For Visual Basic
Imports Microsoft.SqlServer.Management.Smo  
Imports Microsoft.SqlServer.Management.Common

If your code uses Urn functionality, such as Server.GetSqlSmoObject(Urn), you must link to the Microsoft.SqlServer.Management.Sdk.Sfc namespace.

If your code uses the Transfer object directly, you will have to link to the Microsoft.SqlServer.Management.SmoExtended namespace.

When you migrate code, you might have to modify the code. This is because several SQL Server 2005 (9.x) and SQL Server 2008 (10.0.x) features have been deprecated in newer versions of SQL Server. For more information about deprecated features, see Deprecated Database Engine Features in SQL Server 2016.