SQL Audit Login Event not applying filter

When doing a server side trace and capturing the Audit Login Event it seems that it ignores my filter which is based on LoginName.  It still logs any user that logs into the SQL instance whether it is a SQL login or a windows authenticated user.  I just want to know when this specific user logs in successfully.  Is this a known issue?  My filter is as follows:

EXEC sp_trace_setfilter @TraceID, 11, 0, 6, N'XXXXXX'

Please advise.
Gary HarperAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vitor MontalvãoMSSQL Senior EngineerCommented:
I never trusted of those filter by names (LoginName, DatabaseName, ...). Did you try to filter by LoginID instead?
Marten RuneSQL Expert/Infrastructure ArchitectCommented:
Try adding % Before and after the username like:
EXEC sp_trace_setfilter @TraceID, 11, 0, 6, N'%XXXXXX%'

Put in your name instead and make sure it captures you, now change and verify that it doesn't capture you.

Regards Marten

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Gary HarperAuthor Commented:
I do not see a LoginID as a column filter available for Audit Logon.  I had tried adding the % as well and it still behaves the same.
Vitor MontalvãoMSSQL Senior EngineerCommented:
Sorry, it's LoginSID.
Gary HarperAuthor Commented:
Got this working now.   I noticed that when I ran profiler with the events and filter selected it ran properly.  It seems when we add the specific User Error Message error code as a filter it effects the audit login to where it ignores LoginName.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.