Skip to main content

Teradata Architecture

We have many relational databases available in market, teradata is one such RDBMS it is usually preferred when we are dealing data with tera bytes in size and when we need a very fast quick response for retrieval data.

Teradata main advantage is its parallelism architecture and utilities.Lets get to know more about it in a deeper way



we have Parsing engine which has 4 components
a)Session control- It checks for user/login credentials before processing the query
b)Parser-It checks for the SQL syntax and user rights to access various database objects referred in the SQL query submitted by user
c)Optimizer-It generates the query execution plan
d)Dispatcher-It passes execution plan to bynet and receives all the responses and sends back to user

Next we have Bynet it is the communication layer between PE (parsing engine) and AMP's ( access module processors).There are two bynets available Bynet-0 and Bynet-1 which help in continuous communication between AMP's and PE

The final and the most important component is AMP. It is considered as heart of teradata. AMP's are the one which do retrieval and processing the data. Each AMP is connected to its virtual disk where data is stored.They work on their vdisks and do not have to access to other amps vdisks
More the number of AMP's the better will be performance

Hope this article helps you in understanding teradata architecture in the coming posts we will see about 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',...

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