SQL Analysis Overview

You may also like...

5 Responses

  1. December 6, 2011

    […] add. You never want to drop base commerce indexes, but adding indexes is certainly reasonable. See this blog entry on analyzing SQL and this one on identifying problem […]

  2. January 10, 2012

    […] I’ll actually cover this in a post on how to analyze SQL. You cannot usually just copy the SQL out of a stored procedure to explain it – it requires […]

  3. January 17, 2012

    […] Ember Crooks on January 17, 2012 Digg DiggSo the basics of analyzing SQL on db2 are in my post on Analyzing SQL. I wanted to go a bit beyond the […]

  4. March 30, 2012

    […] SQL Analysis Overview […]

  5. June 11, 2013

    […] The first step in generating an Explain Plan in this environment is to put the SQL statement in a file. I also prefer to fully qualify (with schema names) the tables in my SQL while I’m doing this. Fully qualified schema names are not required – I get them ready because I’m frequently doing a db2advis on the query immediately after generating the Explain Plan. db2advis is easier to run with fully qualified table names. For information on how to run db2advis, see SQL Analysis Overview. […]

Leave a Reply

Your email address will not be published. Required fields are marked *