Skip to main content

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

Popular posts from this blog

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...

Synchronous and Asynchronous execution in ODI

In data warehouse designing, an important step is to deciding which step is before/after. Newly added packages and required DW data must be analyzed carefully. Synchronous addings can lengthen ETL duration. Interfaces, procedures without generated scenario cannot be executed in parallel. Only scenario executions can be parallel in ODI. Default scenario execution is synch in ODI. If you want to set a scenario to executed in parallel then you will write “-SYNC_MODE=2″ on command tab or select Synchronous / Asynchronous option Asynchronous in General tab. I have created a package as interfaces executes as; INT_JOBS parallel  INT_REGIONS synch  INT_REGIONS synch  INT_COUNTRIES synch  INT_LOCATIONS parallel  INT_EMPLOYEES parallel (Interfaces are independent.) Selecting beginning and ending times and durations from repository tables as ODI 11g operator is not calculating these values. It is obvious in ODI 10g operator. SELECT    sess_no...

Oracle Data Integrator tools: OdiFileDelete and OdiOutFile

Hello everyone! It’s time for another cool ODI tutorial. Last time, I spoke about the   OdiZip tool and how it can be used to create zip files from a directory. Through this post, I will talk about two more tools related to  Files  namely  OdiFileDelete and  OdiOutFile . 1. OdiFileDelete The  OdiFileDelete  is a tool used to delete files present in a directory or a complete directory on the machine running the agent. Usage OdiFileDelete -DIR=<dir> | -FILE=<file> [-RECURSE=<yes|no>] [-CASESENS=<yes|no>] [-NOFILE_ERROR=<yes|no>] [-FROMDATE=<fromdate>] [-TODATE=<todate>] If  -FROMDATE  is omitted, all files with a modification date earlier than the  -TODATE  date will be deleted. If  -TODATE  is omitted, all files with a modification date later than the  -FROMDATE  date will be deleted. If both parameters are omitted, all files matching the  -FILE...