Post reply

SQL Profler trace related

  • November 19, 2018 at 8:40 am

    #378641

    I am trying to troubleshoot and application issue. In the Database VM that we are using, has  several databases. How can I know my particular database from the SQL Profiler trace.? 

  • November 19, 2018 at 9:02 am

    #2013970

    Profile has been deprecated for some time now. Why not use an Extended Event and add a filter on the database name; setting the value to said database.

    Thom~

    Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
    Larnu.uk

  • November 19, 2018 at 9:18 am

    #2013976

    Thom A - Monday, November 19, 2018 9:02 AM

    Profile has been deprecated for some time now. Why not use an Extended Event and add a filter on the database name; setting the value to said database.

    Okay. Thanks for the info. I will do that.

  • November 19, 2018 at 9:18 am

    #2013977

    Not only has Profiler been deprecated (since 2008), but Server Side trace has also been deprecated now since SQL 2012. You will get so much more value and efficiency from using an Extended Events trace.
    You can set multiple useful filters on the XE session unlike profiler.
    If you are interested in figuring out XE, I recommend this series of articles.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

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

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