17 Best practices for writing optimized SQL queries

Follow 17 Best practices for writing optimized SQL queries:

1. Use EXISTS in place of IN wherever possible

2. Use table aliases with columns when you are joining multiple tables

3. Use groupby instead of distinct.

4. Add useful comments wherever you write complex logic and avoid too many comments.

5. Use joins instead of subqueries when possible for better performance.

6. Use WHERE instead of HAVING to define filters on non-aggregate fields

7. Avoid wildcards at beginning of predicates (something like '%abc' will cause full table scan to get the results)

8. Considering cardinality within GROUP BY can make it faster (try to consider unique column first in group by list)

9. Write SQL keywords in capital letters.

10. Never use select *, always mention list of columns in select clause.

11. Create CTEs instead of multiple sub queries , it will make your query easy to read.

12. Join tables using JOIN keywords instead of writing join condition in where clause for better readability.

13. Never use order by in sub queries , It will unnecessary increase runtime.

14. If you know there are no duplicates in 2 tables, use UNION ALL instead of UNION for better performance

15. Always start WHERE clause with 1 = 1.This has the advantage of easily commenting out conditions during debugging a query.

16. Taking care of NULL values before using equality or comparisons operators. Applying window functions. Filtering the query before joining and having clause.

17. Make sure the JOIN conditions among two table Join are either keys or Indexed attribute.

Comment down below your thoughts if you want to add more points.

Comments

ODI KM Adding Order by Option

You can add Order by statement to queries by editing KM.I have edited IKM SQL Control Append to provide Order by. 1) Add an option to KM named USE_ORDER_BY, its type is Checkbox and default value is False. This option determines you want an order by statement at your query. 2)Add second option to KM named ORDER_BY, type is Text. You will get order by values to your query by this option. 3) Editing Insert New Rows detail of KM. Adding below three line code after having clause. That's it! <% if (odiRef.getOption("USE_ORDER_ BY").equals("1")) { %> ORDER BY <%=odiRef.getOption("ORDER_BY" )%> <%} %> If USE_ORDER_BY option is not used, empty value of ORDER_BY option get error. And executions of KM appears as such below; At this execution, I checked the KM to not get errors if ORDER_BY option value is null. There is no prove of ORDER BY I'm glad. Second execution to get Ord

Creating Yellow Interface in ODI

Hello everyone! In Oracle data integrator (ODI), an interface is an object which populates one datastore, called the target , with data coming from one or more other datastores, known as sources . The fields of the source datastore are linked to those in the target datastore using the concept of Mapping . Temporary interfaces used in ODI are popularly known as Yellow Interfaces . It is because ODI generates a yellow icon at the time of creation of a yellow interface as opposed to the blue icon of a regular interface. The advantage of using a yellow interface is to avoid the creation of Models each time you need to use it in an interface. Since they are temporary, they are not a part of the data model and hence don’t need to be in the Model. So let’s begin and start creating our yellow interface! Pre-requisites : Oracle 10g Express Edition with *SQL Plus, Oracle Data Integrator 11g. Open *SQL Plus and create a new table Sales in Oracle. You can use any existing ta

Running Count in Talend Open Studio

Most Talend components keep a count of the records processed using variables like NB_LINE or NB_LINE_OK. But these are only available after all processing is completed. Define your own counter variable to keep a running count for use in a tMap. Variables like tFilterRow.NB_LINE or tAccessOutput.NB_LINE_INSERTED can be used to report the number of affected lines after a subjob's processing. However, it may be of use to get the current line index for use in a tMap. The index variables used to form NB_LINE aren't available during processing; they're only written out the globalMap at the end of processing. In this example, staging records are loaded from Excel to Access. The order in which the Excel records are read is preserved in a database column called DISPLAY_SEQ_NB. Note that there is an auto-increment column used for record ID in the Access table. This could be used to infer a loading order, but this job uses a separate column to keep the ID as a meaningless surr

TechWare

Search This Blog