Skip to main content

TERADATA UTILITIES

One of the primary reasons why TERADATA is considered such a valuable product in market because of the utilities that are provided by teradata database.
They are five teradata utilities available They are a)BTEQ b)FAST EXPORT c)MLOAD d)FLOAD e)TPUMP

Let me give an overview about these utilities

a)BTEQ - It stands for basic teradata query. In BTEQ we can perform various DDL and DML operations i.e. create,insert,merger,update,delete.
 It can be run in two modea i.e. interactive and batch mode.
 In here we can use BT & ET functions these represent begin transaction and end transaction respectively.
 We can write multiple sql statement with in these two and commit action will be performed upon successful execution of all statements
 If any of the sql statements fails then the data will be roll-backed.

b)FAST EXPORT - FastExport ,the name itself is spells to exports data from Teradata to a Flat file.
But BTEQ also does the same thing.The main difference is BTEQ exports data in rows and FastExport exports data in 64K block so it does super fast
FastExport only supports the SELECT statement.

c)MLOAD - MLOAD means multiload
Load, update and delete large tables in Teradata in a bulk mode
Multiple tables can be loaded at a time.
Updates data in a database in a block mode
Duplicate rows allowed

d)FLOAD - FLOAD means fast load
The target tables must be empty in order to use Fast Load
Supports inserts only - it is not possible to perform updates or deletes in Fast Load
Although Fastload uses multiple sessions to load the data, only one target table can be processed at a time
Teradata Fast load does not support join indexes, foreign key references in target tables and tables with secondary index defined.
It is necessary to drop any of the constraints listed before loading and recreate them afterwards.
Duplicate rows are not allowed

e)TPUMP - It stands for teradata parallel data pump
Main use: to load or update a small amount of target table rows
Sends data to a database as a statement which is much slower than using bulk mode
TPump uses row-level hash locks
TPump does not support MULTI-SET tables.

Hope this article helps you in understanding basic functionalities of teradata utilities

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',

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.