Explore topic-wise InterviewSolutions in .

• It allows US to write SQL STATEMENTS along with BTEQ COMMANDS. We can use BTEQ for importing, exporting and reporting purposes.
• The commands start with a (.) dot and can be terminated by using (;), it is not mandatory to use (;).
• BTEQ will assume any thing written with out a dot as a SQL statement and requires a (;) to TERMINATE it.

CREATE table Customerdummy as CUSTOMER with DATA / with no data

Create table Customerdummy as Customer with data / with no data

LOGON tdipid/username, PASSWORD.

Logon tdipid/username, password.

No, because they become a single AMP OPERATION and my COMPANY didn’t encourage that.

No, because they become a single amp operation and my company didn’t encourage that.

Sub string is used with char FIELDS. So it cannot be used. To extract month from a DATE COLUMN, ex select extract (month from ). Same THING for year or day. Or hour or minutes if it’s a time stamp (select extract (MINUTE from column name).

Sub string is used with char fields. So it cannot be used. To extract month from a date column, ex select extract (month from ). Same thing for year or day. Or hour or minutes if it’s a time stamp (select extract (minute from column name).

FALLBACK REQUESTS that a second copy of each ROW INSERTED into a table be stored on another AMP in the same cluster. This is done when AMP goes down or disk fails.

FALLBACK requests that a second copy of each row inserted into a table be stored on another AMP in the same cluster. This is done when AMP goes down or disk fails.

Group by those FIELDS and SELECT ID, COUNT(*) from table group by id having count (*) > 1.

Group by those fields and select id, count(*) from table group by id having count (*) > 1.

CASE value_expression_1 WHEN value_expression_n THEN scalar_expression_n

END;

CASE value_expression_1 WHEN value_expression_n THEN scalar_expression_n

END;

• TERADATA PERFORMANCE and workload.
• Client platform TYPE, performance and workload.
• Channel performance for channel attached systems.
• Network topology and performance for network attached systems.
• Volume of DATA to be processed by the application.

• Real-time data warehousing is a combination of two THINGS:
• real-time ACTIVITY and
• data warehousing.
• Real-time activity is activity that is happening right now. The activity could be anything such as the sale of widgets. Once the activity is complete, there is data about it. Data warehousing captures BUSINESS activity data. Real-time data warehousing captures business activity data as it OCCURS. As SOON as the business activity is complete and there is data about it, the completed activity data flows into the data warehouse and becomes available instantly. In other words, real-time data warehousing is a framework for deriving information from data as the data becomes available.

The difference between real time and near real time can be summed up in one word: latency. Latency is the time LAG that is between an ACTIVITY completion and the completed activity DATA being available in the data WAREHOUSE. In real time, the latency is negligible whereas in near real time the latency is a tangible time frame such as TWO hours.

The difference between real time and near real time can be summed up in one word: latency. Latency is the time lag that is between an activity completion and the completed activity data being available in the data warehouse. In real time, the latency is negligible whereas in near real time the latency is a tangible time frame such as two hours.

The three-tier differs from the two-tier architecture by strictly enforcing a logical separation of the graphical user interface, business logic, and data. The three-tier is WIDELY used for data WAREHOUSING today. Organizations that REQUIRE greater performance and scalability, the three-tier architecture may be more appropriate. In this architecture, data extracted from legacy systems is cleansed, transformed, and stored in high –speed database SERVERS, which are used as the target database for front-end data access.

The three-tier differs from the two-tier architecture by strictly enforcing a logical separation of the graphical user interface, business logic, and data. The three-tier is widely used for data warehousing today. Organizations that require greater performance and scalability, the three-tier architecture may be more appropriate. In this architecture, data extracted from legacy systems is cleansed, transformed, and stored in high –speed database servers, which are used as the target database for front-end data access.

Data in a Database is Detailed or Transactional, Both READABLE and WRITE able and current.

Data in data WAREHOUSE is detailed and summarized, storage place for HISTORICAL data.

Data in a Database is Detailed or Transactional, Both Readable and Write able and current.

Data in data warehouse is detailed and summarized, storage place for historical data.

• Get BUSINESS requirements.
• CREATE High LEVEL Conceptual Data Model.
• Create Logical Data Model.
• Select target DBMS where data-modeling tool CREATES the physical schema.
• Create standard ABBREVIATION document according to business standard.

There are 12 codd’s RULES applied to the TERADATA database.

There are 12 codd’s rules applied to the teradata database.

If the teradata is going to be only a DATA base means It won’t change the System DEVELOPMENT life CYCLE (SDLC).

If you are going to use the teradata utilities then it will change the Architecture or SDLC.

If your SCHEMA is going to be in 3NF then there won’t be huge in change.

If the teradata is going to be only a data base means It won’t change the System development life cycle (SDLC).

If you are going to use the teradata utilities then it will change the Architecture or SDLC.

If your schema is going to be in 3NF then there won’t be huge in change.

Just like channel driver, TERADATA Gateway acts as a medium of communication between the Parse Engine and applications that are ATTACHED to network clients. Only ONE Gateway is assigned PER node.

Just like channel driver, Teradata Gateway acts as a medium of communication between the Parse Engine and applications that are attached to network clients. Only one Gateway is assigned per node.