Skip to main content

Steps to write SQL queries effectively to improve performance


1)      If you want to join a table using INNER JOIN, Do it as a first step in SQL.
2)      Whenever you join tables, give join conditions in below order
                                I.            Condition on Integer (number) fields
                              II.            Condition on String (Character) fields
                            III.            Range conditions (Like >=, <=, BETWEEN, IN etc.)
3)      If you want to join a table using LEFT OUTER JOIN, Do it after INNER JOIN in SQL.
4)      Should not use functions in join conditions (like CASE, SUBSTR, COALESCE etc.).
5)      Add filter condition (WHERE clause) to eliminate unwanted data.
6)      Use derived queries to filter data before joining with another table.
7)      Create an index on most frequently used columns on table.
8)      Collect statistics on index fields and join columns.
9)      Select only useful fields in SELECT clause.
Example:

SELECT
(Useful fields)
FROM Table1
INNER JOIN Table2
ON (Condition on integer fields if any)
AND (Condition on character fields if any)
AND (condition on range conditions if any)
INNER JOIN
(
SELECT (Useful fields) FROM Table3
WHERE (condition to filter unwanted data)
) Table3
ON (Condition on integer fields if any)
AND (Condition on character fields if any)
AND (condition on range conditions if any)
LEFT OUTER JOIN  Table4
ON (Condition on integer fields if any)
AND (Condition on character fields if any)
AND (condition on range conditions if any)
LEFT OUTER JOIN
(
SELECT (Useful fields) FROM Table5
WHERE (condition to filter unwanted data)
) Table5
ON (Condition on integer fields if any)
AND (Condition on character fields if any)
AND (condition on range conditions if any)

WHERE (Condition to filter unwanted data)

Note: Integer data comparison will be done soon, and after that string comparison will be done soon.
If you have any questions, please feel free to write to kkrishnareddychp@gmail.com

Comments

Popular posts from this blog

Comparing Objects in Informatica

We might face a scenario where there may be difference between PRODUCTION v/s SIT version of code or any environment or between different folders in same environment. In here we go for comparison of objects we can compare between mappings,sessions,workflows In Designer it would be present under "Mappings" tab we can find "Compare" option. In workflow manger under "Tasks & Workfows" tab we can find "Compare" option for tasks and workflows comparison respectively. However the easiest and probably the best practice would be by doing using Repository Manager.In Repository Manager under "Edit" tab we can find "Compare" option. The advantage of using Repository manager it compares all the objects at one go i.e. workflow,session and mapping. Hence reducing the effort of individually checking the mapping and session separately. Once we select the folder and corresponding workflow we Can click compare for checking out ...

Finding Duplicate records and Deleting Duplicate records in TERADATA

Requirement: Finding duplicates and removing duplicate records by retaining original record in TERADATA Suppose I am working in an office and My boss told me to enter the details of a person who entered in to office. I have below table structure. Create Table DUP_EXAMPLE ( PERSON_NAME VARCHAR2(50), PERSON_AGE INTEGER, ADDRS VARCHAR2(150), PURPOSE VARCHAR2(250), ENTERED_DATE DATE ) If a person enters more than once then I have to insert his details more than once. First time, I inserted below records. INSERT INTO DUP_EXAMPLE VALUES('Krishna reddy','25','BANGALORE','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Anirudh Allika','25','HYDERABAD','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Ashok Vunnam','25','CHENNAI','INTERVIEW',TO_DATE('01-JAN-2014',...

Updating Target Table in Informatica

Generally, in every project we will see at least one requirement to update target based on some conditions. Case1: When we have primary key defined on table in Database Case2:   When we do not have primary key defined on table in Database Case3: When we want to update target based on non-primary key field. Let’s discuss it in detail. Case1: When we have primary key defined on table in Database After creating table in DB, import table as target along with primary key constraints. After done with importing, we can check the primary key details by editing target in target definition. In this case, we can use update strategy to update target table. Suppose, we have a table called RETURN_CD and primary key ROW_WID defined on that table. Now, we can update target table using update strategy based on primary key. In mapping, we should connect primary key port and the ports which we want to update in target table. Please check the below screenshot. And ...