Export (0) Print
Expand All

Notification Services Programming Interfaces

SQL Server 2005

Notification Services components use several programming interfaces. This topic contains an overview of the technologies necessary for developing each component.

XML or Notification Services Management Objects

You can define Notification Services applications using XML or the Notification Services Management Objects (NMO).

For more information, see Defining Notification Services Applications.

Transact-SQL

Transact-SQL queries are used to create application rules, which govern notification generation as well as maintenance of application data within a Notification Services instance. Transact-SQL statements can also be used in the definitions of indexes and chronicle tables in the ADF.

For more information, see Defining Event Rules and Defining Subscription Rules.

XML or Notification Services Management Objects

You can configure instances of Notification Services using XML or the Notification Services Management Objects (NMO).

For more information, see Configuring Instances of Notification Services.

Notification Services APIs

Managed code classes that allow you to add, update, and delete subscribers, subscriber devices, and subscriptions. These APIs can be used from managed code, and through COM interop from unmanaged code.

For more information, see Developing Subscription Management Interfaces.

Transact-SQL

You can also manage subscribers, subscriber devices, and simple event-driven subscriptions by using Transact-SQL to add, modify, and delete data in subscription management views. Notification Services views. For more information, see Notification Services Views.

XML

Events submitted to the file system watcher event provider must be in XML format.

XSD

The file system watcher event provider requires the developer to provide a SQL-annotated XML schema file that describes the structure of the events contained in the XML files it processes.

For more information, see File System Watcher Event Provider.

Transact-SQL

Transact-SQL event collection stored procedures are automatically created for each Notification Services application that is created. The standard SQL Server event provider uses these stored procedures along with Transact-SQL queries that you provide to submit SQL Server data as events.

For more information, see SQL Server Event Provider.

Transact-SQL

The Analysis Services event provider facilitates monitoring an Analysis Services cube. You can use the Analysis Services event provider to submit events based on a multidimensional expression (MDX) query to a Notification Services application.

For more information, see Analysis Services Event Provider.

XSLT

The standard XSLT content formatter requires one or more XSLT files to apply to the raw notification data in order to produce formatted content. Applications that use custom content formatters are not required to use XSLT.

For more information, see XSLT Content Formatter.

The File and SMTP delivery protocols simply need to be declared in the ICF and configured in each ADF. For examples, see Defining Delivery Channels.

Notification Services APIs

Managed code classes and interfaces allow you to create custom components that interoperate with Notification Services. They can be used from managed code, and through COM interop from unmanaged code.

For more information, see Developing Custom Notification Services Components.

Transact-SQL

Event collection stored procedures and event class views are automatically created for each Notification Services application that is created. You can use these stored procedures and views to submit events to a Notification Services application.

For more information, see Notification Services Stored Procedures (Transact-SQL) and Notification Services Views.

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

Community Additions

ADD
Show:
© 2014 Microsoft