Privileges and views

When you create a view, the database server tests your discretionary access privileges on the underlying tables and views. When you use a view, however, only your privileges on that view are tested.

After access privileges on tables referenced in view definitions are modified, the database server does not automatically apply to existing views whatever changes were made to access privileges on the underlying tables. To force modified privileges on any table from which the view is derived to apply also to the view, use the DROP VIEW and CREATE VIEW statements of SQL to drop and recreate the view.

Dropping a view also destroys any other views and INSTEAD OF triggers whose definitions depend on that view. After you drop and recreate a view to synchronize its access privileges with those of its underlying tables, you can use the CREATE TRIGGER and CREATE VIEW statements to recreate, respectively, any INSTEAD OF triggers and dependent views that the database server destroyed when you dropped the view.