The user conducting a session that accesses an row level security table may need OVERRIDE privileges if:
- The CONSTRAINT object associated with a constraint column in the table does not define a UDF for the SQL operation.
- Accessing table rows or setting row level constraint values cannot be done effectively with the assigned user defaults.
When an OVERRIDE is in effect for a session:
- The OVERRIDE privileges bypasses enforcement of the affected UDFs.
- If the operation is an INSERT or UPDATE, the user SQL must supply the values to be entered into the named constraint column in the table, either using data from the source table or values specified in a SET SESSION CONSTRAINT statement.
For additional information on OVERRIDE privileges, see Working with Constraint OVERRIDE Privileges.