Teradata Connection

Teradata Connection Skill

On Entry

Tell the user:

Setting up Teradata connection — I'll configure and test a connection to your source Teradata database. This requires a driver download on first use.

Prerequisites

• Network access to the Teradata database instance
• Teradata credentials (username/password) — standard or LDAP-backed
• The scai CLI installed and available
• The Teradata .NET driver NuGet package (Teradata.Client.Provider.nupkg) — see Step 1

Required Connection Details

Workflow

Step 1: Provision the Teradata Driver

The required driver is the Teradata.Client.Provider NuGet package. Resolve it by following the canonical bootstrap flow:

Driver bootstrap: see ../references/driver-bootstrap.md with parameters <dialect>=teradata, <package>=Teradata.Client.Provider, <driver_file>=Teradata.Client.Provider.nupkg, <cache_dir>=~/.snowflake/scai/drivers/teradata/, <nuget_url>=https://www.nuget.org/api/v2/package/Teradata.Client.Provider.

That doc walks through cache check → ask-on-miss → user-provided path or download → first SCAI invocation with --driver-path if needed. Follow it silently — don't narrate "the bootstrap flow" or step labels to the user.

Naming guard: the driver is a .NET NuGet package, not a JDBC driver. Refer to it only as "the Teradata driver" or "the Teradata NuGet package" when talking to the user.

For this skill specifically, the first SCAI invocation called out by the bootstrap is the configure tool call in Step 4 below — pass driver_path=<PATH> there if the driver wasn't already cached. The MCP server invokes scai connection test --driver-path <PATH> internally, which seeds the driver cache.

Step 2: Ask How to Provide Credentials

Ask the user:

"I need the following to connect to Teradata:

• Host (hostname or IP)
• Database name
• Username and Password
• Authentication method — standard (username/password) or ldap (LDAP-backed credentials)

How would you like to provide these?"

Options:

1. Enter manually - Provide values interactively

Step 3: Add the Connection (Manual Entry)

Interactive mode (recommended):

scai connection add-teradata

Inline mode (standard auth):

scai connection add-teradata \
  -s <CONNECTION_NAME> \
  --auth standard \
  --host <HOST> \
  --database <DATABASE> \
  --port 1025 \
  --user <USERNAME>

Inline mode (LDAP auth):

scai connection add-teradata \
  -s <CONNECTION_NAME> \
  --auth ldap \
  --host <HOST> \
  --database <DATABASE> \
  --user <USERNAME>

Password will be prompted securely.

Step 4: Save and Test Source Connection

This is the "first SCAI invocation" called out as 1e in the bootstrap reference. Use the path resolved in Step 1.

Call the configure tool with source_connection set to <CONNECTION_NAME>. The MCP server runs scai connection test internally and only persists the connection if the test passes.

• First use (driver not yet cached): also pass driver_path=<PATH_TO_NUPKG>. The first call copies the driver into ~/.snowflake/scai/drivers/teradata/, so every subsequent configure call (in this project or any other) can omit driver_path.

  configure(source_connection=<CONNECTION_NAME>, driver_path=<PATH_TO_NUPKG>)
  

• Driver already cached: omit driver_path.

  configure(source_connection=<CONNECTION_NAME>)
  

• On success: the response includes connection_test: ok.

• On failure: the tool returns an error containing the scai message. Surface it to the user, help them fix the issue, then re-run configure(...). See ./references/REFERENCE.md for detailed troubleshooting.

Common errors:

CHECKPOINT

Confirm with user:

• Teradata driver resolved via one of:
  • Already cached in ~/.snowflake/scai/drivers/teradata/ (Step 1a)
  • User-provided local path supplied via driver_path (Step 1c)
  • Downloaded by the agent and supplied via driver_path (Step 1d)
• configure returned connection_test: ok
• Connection appears in scai connection list -l teradata --json
• Source connection saved to session config

Supported Operations

Teradata is a full-migration source (project_type: full_migration). After connection setup:

• Code pipeline: scai code extract, scai code convert, scai code deploy
• 2-sided testing: scai test capture, scai test validate (baseline capture and Snowflake result comparison)
• Cloud table data: scai data migrate and cloud data validation via the Data Exchange Worker

For cloud data paths, align worker TOML [connections.source.teradata].database with workflow YAML source.databaseName (the --database value from this connection). LDAP connections map to worker TOML authentication = "LDAP". See ./references/REFERENCE.md for worker setup and troubleshooting.

Legacy projects: If an older project has project_type: code_conversion_only in project.yml, the CLI honors that setting and routes through the code-conversion-only flow. New Teradata projects default to full_migration.

On Completion

After the CHECKPOINT passes, tell the user:

Connection configured — Successfully connected to Teradata using connection <connection_name>.

Then return to the calling skill.

Security Rules

• NEVER log or display passwords in plain text
• NEVER include passwords in command-line arguments that might be logged
• Use interactive mode to avoid password exposure

Quick Reference