A powerful use of symbolic
substitution is to deploy row-level security on sensitive tables that
use views. Suppose that only certain users or groups can access a
sensitive table. You can use symbolic substitution to create a single
view to the table that provides restricted access based on user ID
or groups. You can grant Universal access to the view, but only users
or groups that meet the symbolic substitution constraints can see
the rows.
For another example,
imagine a table that contains sensitive information has a column that
contains group names or user IDs. You can use symbolic substitution
to create a single view that allows users to access only the rows
that contain their user ID or group. You can grant Universal access
to the view, but each user or group is allowed to see only their user
or group rows.
CAUTION:
SPD Server
SQL symbolic substitution uses an 8-byte literal string (blank padded
if necessary) to replace SPD Server user and SPD Server group names.
Symbolic substitution will not match a column that is less than 8
characters wide. If the table column that contains user IDs or group
names is not at least 8 characters wide, symbolic substitution will
evaluate the WHERE- predicate on that column to be FALSE, which can
result in incorrect results.