Database Tuning Advisor not giving recommendations for large query

  • During this incident I used Idera's SQL Diagnostic Manager and SQL Doctor. SQL DM showed there was a big problem because the wait stats were huge. I could tell that performance was very poor from that. I've found SQL DM to be very helpful in monitoring over 30 SQL Servers. I used SQL Doctor to get a rough idea of what indexes might be needed. Neither of these gave me the perfect answer but having helpful tools makes life easier. But both require you to understand the recommendations they give. For the most part, I didn't implement any suggestions I didn't understand.

  • Do you use 'sub-query'? from my try, DTA doesn't drill down into sub-query. I cheated the DTA while tuning by moving sub-query to main query, DTA gave different result.

  • Yes, there was a sub-query. I didn't know DTA wouldn't parse that. Thanks!

  • It Depends. I'm pretty sure that DTA evaluates everything that it can "see". That means that the sub-query has to be one that acts more like an inline view than something separate. If it couldn't process sub-queries, it wouldn't be able to evaluate CTE's or derived tables or cross apply or.... and it does all of that quite nicely.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 4 posts - 46 through 48 (of 48 total)

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