CREATE SERVER AUDIT with predicate filter succeed even with missing filter - by Flair

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


3
0
Sign in
to vote
ID 3135313 Comments
Status Resolved Workarounds
Type Bug Repros 0
Opened 6/6/2017 11:11:11 AM
Access Restriction Public

Description

According to https://docs.microsoft.com/en-us/sql/t-sql/statements/create-server-audit-transact-sql we have created a server audit with a predicate filter. Due to internal reasons the predicate accidently exceeds the limit of nvarchar( 3000 ). The creation was possible without any error - but the create server audit should fail with error message if the predicate is to large and the audit did not work
By the way: our filter would not exceed the limit when the audit would allow an IN ( list of conditions ) instead of cascading OR statements
Sign in to post a comment.
Posted by Tomer Levav (Microsoft) on 6/12/2017 at 10:30 AM
Hi Flair,
You're are right, the expected behaviour in this case should be failing the CREATE AUDIT statement.
We'll work on a fix and we'll publish it in one of the future releases.

Thank you for bringing this issue to our attention,
Tomer Levav (MSFT)