SqlStatement Element for EventClass/Chronicles/Chronicle/SqlSchema (ADF)

Contains a Transact-SQL statement for an event chronicle table.

Syntax

<EventClasses>
    <EventClass>
        ...
        <Chronicles>
            <Chronicle>
                    ...
                    <SqlSchema>
                        <SqlStatement>

Element Characteristics

Characteristic Description

Data type

string, between 0 and 100,000 characters in length.

Default value

None.

Occurrence

Optional once or more per SqlSchema element.

Updates

Can be added, deleted, and modified when updating the application.

Element Relationships

Relationship Elements

Parent element

SqlSchema Element for EventClass/Chronicles/Chronicle (ADF)

Child elements

None.

Remarks

Use Transact-SQL statements to create the event chronicle table used to store supplemental event data.

When using a chronicle you should include one SqlStatement element that drops or renames the chronicle table if it already exists and one SqlStatement element that re-creates the chronicle table. If you do not drop or rename an existing chronicle table, you will receive an "object exists" error when you update the application. For an example, see SqlSchema Element for EventClass/Chronicles/Chronicle (ADF).

You may also want to have SqlStatement elements for indexes.

Example

The following example shows a SqlStatement element that drops the event chronicle table StockEventChron if it exists.

<SqlStatement>
IF EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLES
    WHERE TABLE_NAME = 'StockEventsChron'
        AND TABLE_SCHEMA = 'dbo')
    DROP TABLE dbo.StockEventsChron;
</SqlStatement>

See Also

Reference

Application Definition File Reference

Other Resources

Defining Event Chronicle Tables
Updating Instances and Applications

Help and Information

Getting SQL Server 2005 Assistance