Defining the Core Subscription Class
A subscription class defines one type of subscription for your application. When you define a Notification Services application, you must create one subscription class for each type of subscription that is supported by your application.
When Notification Services creates the application, it creates tables, views, basic indexes, and stored procedures for the subscription class. The core subscription class properties define the names and locations for these database objects.
The Core Subscription Class
All subscription classes have the following user-defined properties:
- A subscription class name.
- A filegroup, which specifies where Notification Services creates the subscription class objects in the application database.
Optionally, you can define a subscription class schema, event rules, scheduled rules, custom indexes, and subscription chronicle tables. Most subscription classes have at least a schema and a rule.
Notification Services automatically adds the following:
- SubscriptionId, SubscriberId, Created, Updated, and Enabled fields in the resulting subscription class table.
- If the subscription class has scheduled rules, a ScheduleId field in the subscription class table and an index on this field.
To define a subscription class
If you are defining an application through XML, define subscription classes in the application definition file (ADF). If you are defining an application programmatically, use Notification Services Management Objects (NMO) for to define subscription classes.
Naming the Subscription Class
Each subscription class in an application must have a unique name. This name is used to create application objects and for running administrative reports.
To define a subscription class name
- SubscriptionClassName Element (ADF)
- SubscriptionClass constructor (NMO)
Specifying the Filegroup
Subscription class database objects can be placed in a non-default filegroup.
If you define the application database, the specified filegroup must match one of the named file groups in the database definition. For more information, see Defining the Application Database.
If the application database already exists, the specified filegroup must exist in the application database.
If you do not specify a filegroup, subscription class objects are automatically created on the default filegroup for the application database.
For more information about filegroups, see Using Files and Filegroups.
To define the subscription class filegroup
See Also
Concepts
Defining the Subscription Schema
Defining Subscription Rules
Defining Indexes for a Subscription Class
Defining Chronicles for a Subscription Class
Collecting Subscription-Related Information