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

Target Load Type - Normal or Bulk in Session Properties

We can see the Target load type ( Normal or Bulk) property in session under Mapping tab and we will go for Bulk to improve the performance of session to load large amount of data. SQL loader utility will be used for Bulk load and it will not create any database logs(redolog and undolog), it directly writes to data file.Transaction can not be rolled back as we don't have database logs.However,Bulk loading is very as compared to Normal loading. In target if you are using Primary Key or Primary Index or any constraints you can't use Bulk mode. We can see this property in the below snap shot.

SCD Type 2 Implementation in Informatica using dynamic lookup

We have already covered how a dynamic look up works the same can be found out from the following link http://dwbuddy.blogspot.com/2014/06/dynamic-look-up-in-informatica.html  So let's see how we can use it in a regular SCD type 2 mapping. The logic used in SCD type 2 is same as discussed in earlier blog i.e.  http://dwbuddy.blogspot.com/2015/01/scd-type-ii-implementation-in.html . The only difference being here is we have used dynamic look up instead of a static one. We go for dynamic look up when there are duplicate entries for a PK value and only the latest record present in the file should be termed as active. Let us consider the following sample data So  for EMP_ID 101 we have two records in the same day flow so the latest record i.e. with salary as 1500 should be termed as Active record. The mapping will look in the following way So in here we have a dynamic lookup couple of expression transformations,a transaction control transformation which is use...