InputSchema Element (ADF)

Specifies the database schema name for the condition action's input.

Syntax

<ConditionAction>
    ...
    <InputSchema>

Element Characteristics

Characteristic	Description
Data type	string, between 1 and 128 characters in length.
Default value	The application's schema. The default application schema is dbo.
Occurrence	Optional once per ConditionAction element. If you do not specify the input schema, the input must be in the application's schema.
Updates	You can modify, add, or delete this element when updating the application. Modifying the input schema or name is equivalent to deleting and then adding the rule.

Element Relationships

Relationship	Elements
Parent element	ConditionAction Element (ADF)
Child elements	None.

Hinweise

When you use a condition action, you must specify which view or table contains the event data. This view or table is in a schema.

• If the input is the view named after the event class, the schema is the application schema. The application schema can be specified when defining the application database, or it can be the default value of dbo. For more information, see Definieren der Anwendungsdatenbank.
• If the input is an event chronicle, the schema is defined in the CREATE TABLE statement that creates the event chronicle. This is usually the same as the application schema. For more information, see Definieren von Verläufen für eine Ereignisklasse.

For more information about condition actions, see Definieren von Bedingungsaktionen.

Beispiel

The following example shows how to define a condition action. The query in the Transact-SQL expression selects data from the MyAppSchema.WeatherEventRule view, which contains data from the subscription class and from the MyAppSchema.WeatherEvents event view.

<ConditionAction>
    <SqlLogin>[MyLowPrivLogin]</SqlLogin>
    <SqlUser>[MyLowPrivUser]</SqlUser>
    <InputName>WeatherEvents</InputName>
    <InputSchema>MyAppSchema</InputSchema>
    <SqlExpression>
        INSERT INTO MyAppSchema.WeatherNotifications(SubscriberId, 
        DeviceName, SubscriberLocale, City, Forecast) 
        SELECT [Subscription.SubscriberId], [Subscription.DeviceName], 
            [Subscription.SubscriberLocale], [Input.City], 
            [Input.Forecast])
        FROM MyAppSchema.WeatherEventRule;
    </SqlExpression>
</ConditionAction>

Siehe auch

Verweis

Application Definition File Reference

Konzepte

Instance Configuration File Reference

Andere Ressourcen

Definieren von Bedingungsaktionen
Definieren von Abonnementregeln
Trennung von Benutzer und Schema

Hilfe und Informationen

Informationsquellen für SQL Server 2005