Restrictions on Updating Data Through Views You can insert, update, and delete rows in a view, subject to the following limitations: If the view contains joins between multiple tables, you can only insert and update one table in the view, and you can't delete rows.You can't directly modify data in views based on union queries.

updating data in a view sql-80

When SCHEMABINDING is specified, the base tables cannot be modified in a way that would affect the view definition.

The view definition itself must first be modified or dropped to remove dependencies on the table to be modified.

Browse-mode metadata includes information about the base table that the columns in the result set belong to.

For views created with VIEW_METADATA, the browse-mode metadata returns the view name and not the base table names when it describes columns from the view in the result set. If ALTER VIEW is not used, but instead the view is dropped and re-created, the previously used GRANT statement and any other statements that deal with permissions pertaining to this view must be re-entered.

Bear in mind that a view is not a table and contains no data—the actual modification always takes place at the table level.

Views cannot be used as a mechanism to override any constraints, rules, or referential integrity defined in the base tables.

The view is a portion of data from the underlying tables.

Provided that you have permissions, you can do the same data manipulation in views that you can do to a table directly.

ALTER VIEW can be applied to indexed views; however, ALTER VIEW unconditionally drops all indexes on the view.