Teradata important component (architecture point of view)

 Parsing engine: Receive the query from client and will check the syntax error, user access, receive the result from client and send to client.


Message parsing layer: it will receive the execution plan and send to AMP and will receive the result and will send to Engine.

AMP : SOrting, filtering and data type conversion

Comments

Post a Comment

Popular posts from this blog

General information about Netezza : Default Error details

General information about Netezza : Default Error details     There are around 140 default error details available in Netezza. For your reference please find below details. ERRORCODE ERRORTEXT 1 Operation failed 2 Interaction aborted 3 Statement aborted 4 Could not serialize - transaction aborted 5 Transaction no longer active 6 Out of memory 7 Incorrect data type 8 Illegal value 9 Internal: SPUs crosstalking 10 Internal pipe I/O failed 11 Cannot determine hostname 12 Rogue SPU trying to register 13 No such table exists 14 No such field exists in table 15 Table already exists 16 Plan already exists in plan dictionary 17 F...
Read more

Minus in Teradata?...

Minus : It will provide the result which one is not matching from both tables... Note: It will provide the not matching result from first select table only. Select Emp_No from Emp Minus Select Emp_no from Emp_Dep;
Read more