Starting a Subscription Management Project
The Notification Services subscription management API is written in managed code. You can develop your interfaces in any language supported by the Microsoft .NET Framework common language runtime (CLR). You can also develop in native code through COM interop.
When you start developing your application, you must define the correct assembly references, make sure that the Notification Services instance is registered, and that your interfaces use accounts with the correct permissions. Use the following information to set up your server and your solution.
References
To build a subscription management interface using the Notification Services subscription management API, your code must reference the following assemblies:
- Microsoft.SqlServer.NotificationServices.dll, which is required for all subscription management interfaces.
- Microsoft.SqlServer.NotificationServices.Rules.dll, which is required to manage subscriptions that contain conditions.
When you install Notification Services, these assemblies are registered. The DLL files are located in the Notification Services bin folder. The default location for this folder is C:\Program Files\Microsoft SQL Server\90\NotificationServices\n.n.nnn\bin, where n.n.nnn is the version number.
If you are enumerating instance and application properties, you may need to add a reference to the Microsoft.SqlServer.Management.Smo.dll assembly, which contains the Notification Services Management Objects (NMO). The default location for this assembly is C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies.
Instance Registration
On the server that runs your subscription management interface, you must register the instance of Notification Services. The registration contains information about the Notification Services instance and application databases.
For more information about deploying subscription management applications, see Deploying a Subscription Management Interface.
Windows and SQL Server Authentication
Subscription management interfaces must have the correct permissions to manage subscriber and subscription data.
The account your subscription management interface runs under must be able to log in to the instance of the Database Engine that hosts instance and application databases. The login can use either Windows Authentication or SQL Server Authentication.
The account must be able to log in to the instance and application databases, and must be a member of the NSSubscriberAdmin database role in those databases.
For more information about deploying subscription management applications, see Deploying a Subscription Management Interface.
See Also
Concepts
Subscription Management API
Notification Services Database Roles