Assembly: Microsoft.SqlServer.Smo (in microsoft.sqlserver.smo.dll)
Event chronicles are optional; use them only if you need to maintain event information outside of the event tables used by an event class. A common reason to use an event chronicle is to store and maintain event data for scheduled subscriptions.
Each EventChronicle must have one or more Transact-SQL statements specified using the SqlStatements property.
The following examples show how to define an event chronicle and add it to the collection of chronicles for an event class:
// Define a chronicle for the class EventChronicle ec1 = new EventChronicle(flightEvents, "FlightEventChonicle"); ec1.SqlStatements.Add( "CREATE TABLE MyAppSchema.FlightEventChronicle " + " (LeavingFrom nvarchar(6), GoingTo nvarchar(6), " + " Price float);"); ec1.SqlStatements.Add( "CREATE INDEX FlightEventChronicleIndex " + "ON MyAppSchema.FlightEventChronicle " + "( LeavingFrom, GoingTo );"); flightEvents.EventChronicles.Add(ec1);