On this page
Teradata
Prepare Teradata inputs for a data estate, collect the relevant dependencies, and verify the scope represented in Understand.
modernAIze supports Teradata as a data estate source platform. Collect the SQL and BTEQ scripts that describe the selected processing. Include the definitions needed to interpret referenced tables and views. Data rows alone do not describe the SQL that creates or transforms them.
Inputs to prepare
BTEQ and SQL source in .bteq, .sql, .tsql, or .td files. Delimited sample data in .csv, .dat, and .txt is also accepted. These
extensions are treated as sample data; keep SQL and configuration scripts in
their native source formats.
Native assets and what to collect
| Asset | Material to supply | What it contributes |
|---|---|---|
| BTEQ script | .bteq source | SQL statements plus command and execution-control context |
| SQL script | .sql, .tsql, or .td source | Queries, data manipulation, and preparation steps |
| Table or view definition | DDL text in the supported SQL source files | Columns and the definitions behind referenced structures |
| Stored procedure | Source definition | Procedural behavior and embedded SQL |
| Teradata macro | Source definition | Reusable SQL processing |
| Sample data | Approved delimited .txt, .csv, or .dat files | Sample-data columns and input context; not a general prose or configuration reader |
Collect definitions, not just query results. If a script refers to a view or procedure stored in the database, the script file alone does not contain that object’s implementation.
Keep .sql procedure definitions under procs/ and macro definitions
under macros/. BTEQ configuration belongs under config/; other BTEQ
files describe processing scripts. Use Folder or ZIP to preserve these
paths, because they affect how the source is classified. Do not assume a
procedure or macro placed among ordinary SQL files receives the same treatment.
How to collect the inputs
Copy the controlled SQL and BTEQ source and use the team’s Teradata tooling to retrieve definitions of the selected database objects. Save them as supported text source files. This is manual collection plus native definition export; a separate modernAIze extraction program is not needed for this route.
Keep the intended database names and parameter context clear. Review connection and logon material before transfer. Include the definitions of referenced views when their joins, filters, or calculations are part of the assessment question.
Prepare the source
- Identify the scripts that create or populate the assessment output.
- Collect the BTEQ or SQL source and the relevant table and view definitions in a consistent revision.
- Record parameters and execution context that select databases, dates, or processing branches.
- Identify upstream loads and downstream consumers that are outside the proposed scope.
Investigate the analysis
Follow reads, intermediate structures, and writes to understand the data path. Inspect SQL expressions, joins, filters, and aggregations that determine the result. Where BTEQ controls the processing sequence, consider its execution conditions alongside the SQL statements.
Start with Briefing for the system-level explanation, then use the appropriate Landscape view and available Detail links to investigate the relevant processing. Keep the question tied to the supplied source revision.
Example review question
The following example is synthetic.
For monthly revenue, review the SQL that joins orders to exchange rates and populates the monthly result. If the script reads a view, include the view’s definition when its filtering or calculations affect the output.
Verify the scope
Locate the expected processing and referenced structures in the analysis. Resolve missing view definitions or externally prepared tables according to the assessment question. Preserve execution parameters with any conclusion that depends on them.