Skip to main content

Pre and Post Sql,Session properties at session level

By
Sometimes we may have a requirement where might need to drop indexes/truncate table and then load the data. So in here what we can we do is we can go for pre sql in session properties and there we can write the required the sql statements such as dropping indexes or truncating table and after the loads i.e. session gets completed we can recreate the indexes in post sql command. In mapping also we can do the same but it is advisable to do at session level.




We even have option in session such as Presession, Postsession command and Postsession failure command.

In session go to components tab to find out these options.

Upon requirement we can use the following command to run unix scripts for specific purpose.

We have email option option for on success/failure scenarios too.




Hope this article helps you in understanding post/pre session commands

Comments

  1. UnknownNovember 1, 2017 at 3:24 AM

    I have read your blog and i got a very useful and knowledgeable information from your blog.You have done a great job .I feel happy to read your post, thanks for sharing your knowledge of sap with us keep posting with new concepts...

    Dataware Tools
    HADOOP Training in Chennai
    Base SAS Training in Chennai
    MSBI Training in Chennai
    INFORMATICA Training in Chennai
    DATAWAREHOUSE Training in Chennai

    ReplyDelete

Post a Comment

Popular posts from this blog

Comparing Objects in Informatica

By
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 ...
11 comments
Read more

Finding Duplicate records and Deleting Duplicate records in TERADATA

By Anonymous
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',...
2 comments
Read more

Target Load Type - Normal or Bulk in Session Properties

By
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.
Post a Comment
Read more