Export (0) Print
Expand All

Notification Services Backward Compatibility

SQL Server 2005

The following sections list changes in SQL Server 2005 Notification Services that could affect your existing Notification Services applications.

No Notification Services 2.0 functionality has been discontinued in SQL Server 2005.

SQL Server 2005 Notification Services contains some changes that will cause your existing Notification Services 2.0 applications to stop working when you upgrade to SQL Server 2005. The table below contains the list of known breaking changes.

Breaking change Description

The Notify() function has been removed.

In Notification Services 2.0, you had to use the Notify() function in any subscription rule that generated notifications. For security and performance reasons, the Notify() has been removed. For more information, see Migrating Notification Services 2.0 Instances to SQL Server 2005.

Custom components must be recompiled.

In SQL Server 2005, the strong name of the Notification Services assembly has changed. As a result, you must recompile any custom event providers, content formatters, delivery protocols, and custom applications built using the Notification Services API. When you recompile these components or applications, use the SQL Server 2005 assemblies and .NET Framework version 2.0.

Notification Services instances must use the same version of the Database Engine.

Notification Services 2.0 instances must use the SQL Server 2000 Database Engine. SQL Server 2005 Notification Services instances must use the SQL Server 2005 Database Engine. After you upgrade the Database Engine to SQL Server 2005, you must migrate the instance of Notification Services to SQL Server 2005. For more information, see Migrating Notification Services 2.0 Instances to SQL Server 2005.

There are no significant behavior changes for SQL Server 2005 Notification Services.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft