Know what the Teradata estate contains before you pick a date

What we look at on Teradata

• Tables, including SET versus MULTISET, and the primary indexes that still decide how they are read
• Macros, stored procedures and UDFs, and which of them hide a rule nobody wrote down elsewhere
• BTEQ, FastLoad, MultiLoad and TPT jobs, and the windows they actually run in
• Viewpoint schedules and the downstream consumers that still wait on them
• Character sets and export encodings that have bitten previous extracts
• Volatile tables and staging patterns that look unused until a nightly job misses them

What a person still has to do

• 01Primary indexes are not partitions. Access paths have to be redesigned against how the table is actually queried.
• 02BTEQ, FastLoad, MultiLoad and TPT become an ingestion path we choose. They do not convert.
• 03Macros and procedures stay in the residue until someone reads the business rule inside them.
• 04Viewpoint schedules become Databricks Jobs or Lakeflow. The clock and the dependencies have to be redrawn.
• 05Encoding and export quirks show up in the first extract, which is why the hard-object pilot is chosen early.

What the two weeks produce

• 01An inventory where every object is dispositioned as in scope, excluded, or owned by a person
• 02The exclusions written down and agreed, so the scope still holds when someone questions it in month four
• 03A dependency map and a wave plan that respects it
• 04A named owner against every workload surface
• 05Parity criteria per object type, agreed before any conversion runs
• 06A hard-object pilot, chosen as the thing most likely to break
• 07A go or no-go recommendation with the reasoning shown

The other sources