FIX: Wrong "schema_name" and "class_type" values for the CREATE SECURITY POLICY statement in SQL Server 2016
Content provided by Microsoft
Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise CoreSQL Server 2016 StandardMore
Assume that you enable both Row-Level Security and SQL Server audit on a table in SQL Server 2016. When you execute a CREATE SECURITY POLICY statement, an audit record is created, however, the audit record doesn't have the correct schema_name and class_type values.
The issue was first fixed in the following cumulative update of SQL Server: