Post reply

Performance Tuning a query running since more than 13 minutes

  • August 13, 2014 at 10:22 am

    #1737694

    GilaMonster (8/13/2014)

    faisalfarouqi (8/13/2014)

    Thanks! Gail, but this is the query that they use from the reporting tool for cube refresh

    If it's a cube refresh, then it should be running scheduled out of business hours and so people shouldn't be caring how long it runs. Cube refreshes are maintenance window tasks.

    [font="Comic Sans MS"]This is what they say about this query, so basically they use it for putting the data into MicroStrategy cube, and maybe then work on those cubes later on.

    Regards,

    Faisal

    [/font]

  • August 14, 2014 at 6:11 am

    #1737999

    Luis Cazares (8/13/2014)

    Could this be part of the problem? There's a huge difference between estimated and actual number of rows.

    That's the outer feed for a nested loop so estimated number of rows must be multiplied by the estimated number of executions to compare to actual number of rows.

    There are 16001971 estimated number of executions with an estimated number of rows of 1.39597 so the actual estimate is 22338271 which is not too far off from the actual number of rows.

    The SQL Guy @ blogspot[/url]

    @SeanPearceSQL

    About Me[/url]

Viewing 2 posts - 16 through 16 (of 16 total)

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