Locks an object to the schemas it depends on. Security policies default to ON, meaning nobody's rights on their predicate function get checked; turned OFF, each user requires SELECT or EXECUTE over that function plus anything it touches.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains SCHEMABINDING in context, with comparison tables and the common traps.
Terms in this definition
- Predicate function
The logic behind row-level security. Written as an inline TVF, it yields a row only when the user should see or change the data; tables are bound to it through a security policy, which applies it either to filter rows out or to block writes.
- Get
Key Vault permission on secrets that allows a single secret to be read; App Service Key Vault references need nothing beyond it.
- Chat message roles
Labels on chat messages: instructions go under system, the person's input under user, the model's previous answers under assistant, and results returned by a called tool under tool (or function).
- SELECT
A DML command in SQL used to retrieve rows from one table or several.
- EXECUTE
Allows calling a function or loading a registered model in Unity Catalog, and seeing its definition.
USE CATALOGandUSE SCHEMAare needed too. - OVER
Gives a T-SQL window function its window: PARTITION BY, ORDER BY and, if wanted, a ROWS or RANGE frame. Rankings and running totals can then be worked out while every row is kept.
Related terms
- Indexed view
When a view is given a unique clustered index, SQL Server materialises its output and maintains it much as it would a table. Creating one requires SCHEMABINDING plus particular SET options, and changes to the underlying base tables are applied to it too.