Defining Event Classes
A Notification Services application can either store data in the application database or query other event sources, such as external databases, at run time. Most application developers store event data in the application database to take advantage of operational and administrative efficiencies.
To store event data in an application database, you must define one or more event classes. An event class defines the name, fields, filegroup, indexes, supplemental event tables (event chronicles), and rules that update supplemental tables. If your application uses multiple types of events, such as a sports application that provides statistics for multiple sports, define multiple event classes.
When Notification Services creates the application, it uses the information in each event class to implement SQL Server objects, such as tables and standard indexes, for the event data. Event providers supply data to the event tables. For more information, see Defining Event Providers.
In This Section
| Topic | Description |
|---|---|
Describes a basic event class, containing a name, fields, and a filegroup, with links to topics that describe how to create one. |
|
Describes why you might need to add custom indexes to an event class, with links to topics that describe how to implement them. |
|
Contains information about supplemental event tables, called event chronicles, how event chronicles are useful, and how to implement them. |
See Also
Reference
Other Resources
EventClasses Element (ADF)
Defining Notification Services Applications
Defining Event Providers
Application Definition File Reference
Application Definition File Templates