Post reply

Trace Filter Troubles

  • May 16, 2011 at 2:51 pm

    #251127

    I have a server side trace running, and I wanted to go back and look at reindexing I did last Sunday. I open the trace file from that day: -> Column Filters -> TextData like '%alter index%'

    but I get no results.

    So then I try: LoginName like '%MyName%'

    still no results.

    or

    NTuserName like '%MyName%' and I get thousands of rows with blank NtUserName ?!?!

    So, I export the entire trace file to a SQL table, and run the select there and I get all the results I was expecting. Am I getting my syntax wrong with profiler ?

  • May 16, 2011 at 3:14 pm

    #1325496

    I sounds like you are filtering on the wrong column within the trace? NTUserName vs LoginName...

    Is NTUserName populated?

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • May 16, 2011 at 11:45 pm

    #1325593

    Profiler filters are a pain to work with. Profiler does the opposite with nulls that SQL does.

    Import into a table and query. Far, far easier.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply