Compartir a través de


AddViewsInsteadOfTriggers Procedure (Repository.Item Schema)

[This content is no longer valid. For the latest information on "M", "Quadrant", SQL Server Modeling Services, and the Repository, see the Model Citizen blog.]

Adds INSTEAD OF triggers to a target view that make the view updatable. In addition to supporting insert, update, and delete statements, the triggers also provide Folder based security when using the default filters.

[Repository.Item].[AddViewsInsteadOfTriggers] ( @schema, @view, @insertFilter, @deleteFilter, @updateFilter, @idGeneration, @sequenceSchema, @sequence )

Arguments

@schema

Type: sysname. The schema of the target view.

@view

Type: sysname. The name of the target view.

@insertFilter

Type: nvarchar(max). An optional Transact-SQL string that filters access to the INSTEAD OF insert trigger. The default implementation uses the standard Folder based security.

@deleteFilter

Type: nvarchar(max). An optional Transact-SQL string that filters access to the INSTEAD OF delete trigger. The default implementation uses the standard Folder based security.

@updateFilter

Type: nvarchar(max). An optional Transact-SQL string that filters access to the INSTEAD OF update trigger. The default implementation uses the standard Folder based security.

@idGeneration

Type: tinyint. An integer that defines the type of identity pattern used by the target view. Possible values include 0 for no pattern, 1 for an auto-numbered IDENTITY column, and 2 for sequence objects.

@sequenceSchema

Type: sysname. The schema for the sequence object to use when inserting new rows into the underlying table. This parameter is required only when @idGeneration is set to 2 (sequence object pattern).

@sequence

Type: sysname. The name of the sequence object to use when inserting new rows into the underlying table. This parameter is required only when @idGeneration is set to 2 (sequence object pattern).

Remarks

See Also

Reference

Repository.Item Procedures
Repository.Item Schema

Send comments about this topic to Microsoft.