DWHPro Insights

Teradata SQL Assistant: Connect, Export CSV and Troubleshoot

By Roland Wenzlofsky ·

Teradata SQL Assistant: Connect, Export CSV and Troubleshoot

Teradata SQL Assistant is a Windows desktop client for running SQL, viewing answer sets and exporting results. The documented connection providers are ODBC and the .NET Data Provider for Teradata. Start by matching the client and driver, then test the connection with a small query before exporting data.

Updated 22 October 2026.

Download and installation: what you need

Get the client software from Teradata or your organization’s approved software catalogue. Teradata publishes TTU 17.20 for Windows, but that listing is a release-specific package, not a claim that 17.20 is the newest or correct version for your system. Check package contents, supported Windows versions, database compatibility and access requirements before installing.

SQL Assistant has been distributed through Teradata Tools and Utilities (TTU). Do not assume that every TTU package contains every client, or that installing a Teradata database server database also installs a Windows desktop application. Your database server and SQL Assistant are separate installations.

Before connecting, obtain the database hostname, the required authentication mechanism, network or VPN requirements, and the approved client/provider versions from your DBA. The ODBC driver architecture must match the client application: a 32-bit application needs the corresponding 32-bit driver and DSN, even on 64-bit Windows.

Is Teradata SQL Assistant free?

Check the terms and access requirements for the specific download or your organization’s Teradata entitlement. Availability through a developer download does not establish unrestricted licensing for every deployment. This guide does not treat Teradata database server as a bundled Windows SQL Assistant installer.

Connect SQL Assistant through ODBC

  1. Install the approved ODBC Driver for Teradata matching your SQL Assistant architecture.
  2. Open the matching Windows ODBC Data Source Administrator and create or select a Teradata DSN. Configure the database hostname and other settings required by your environment.
  3. In SQL Assistant, select ODBC from the provider list and use the Connect toolbar button.
  4. Select the DSN. Supply your user ID and the authentication settings your organization requires, or use the configured integrated-security option. Do not assume TD2 is appropriate for an LDAP or single-sign-on environment.
  5. Connect and run the small test query below. Confirm the session before executing queries against application tables.
SELECT CURRENT_DATE AS today;

The result should be one row containing the current date for the session. Its displayed format can depend on the provider and client settings. See Teradata date formatting and conversion if you need a specific output representation.

Teradata Query Performance Tuning: The DWHPro Guide book cover

Get the complete Teradata tuning book, free

Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis

206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.

Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.

About the free book

Connect through the .NET Data Provider for Teradata

  1. Install the supported .NET Data Provider for Teradata required by your client release.
  2. Select Teradata .NET from SQL Assistant’s provider list.
  3. Use Connect, select or define the .NET data source, and enter the server and authentication details required by your organization.
  4. Run the same small query to confirm the connection.

A .NET data source is not an ODBC DSN. Creating a DSN in Windows does not automatically configure the .NET provider. Teradata’s SQL Assistant guide documents ANSI date mode for .NET connections; use date literals such as DATE '2026-10-22' rather than ambiguous date strings.

ODBC, .NET and CLIv2 are different things

The SQL Assistant user guide documents ODBC and Teradata .NET provider connections. CLIv2 means Call-Level Interface Version 2; it is not the name of a command-line interface or an interchangeable provider-list choice in this workflow. For interactive terminal work and batch scripts, see Teradata BTEQ.

Export query results to CSV

Use a small export first so you can verify the delimiter, headings, character encoding and date representation before writing a large file. The following workflow follows Teradata’s SQL Assistant for Windows guide; labels and available options can vary by installed version.

  1. Review the Export/Import settings in the Options dialog. Set a comma delimiter when the receiving system expects comma-separated data, and choose whether column headings are included.
  2. Select File > Export Results to enable export mode.
  3. Enter the SELECT statement in the Query window and execute it.
  4. In the Export File dialog, choose the destination, filename and appropriate file type. A .csv extension alone does not change the delimiter or quoting settings.
  5. Open the output in a text editor or CSV-aware reader. Check headings, column counts and fields containing commas, quotes or line breaks. Confirm that the receiving application parses the same rows and columns.
  6. Turn off File > Export Results when you want subsequent queries to return to the normal answer-set workflow.

Use this single-row query to check date formatting in an export:

SELECT
    1 AS example_id,
    TO_CHAR(DATE '2026-10-22', 'YYYY-MM-DD') AS date_text,
    'example' AS description;

Expected field values are 1, 2026-10-22 and example. The exact CSV quoting and header row depend on your export options. Spreadsheet software may reinterpret dates and identifiers on opening; inspect the file itself before concluding that SQL Assistant changed the values.

Large exports and multiple output files

For a constrained Windows environment, the worked SQL Assistant multi-file export example shows one way to split a large result. For repeatable bulk movement, evaluate Teradata Parallel Transporter instead of relying on a desktop session. Choose the tool based on the workload, operational controls and available access.

Troubleshooting connections and exports

SymptomWhat to check
The DSN is missingConfirm the ODBC provider is selected and that the DSN and driver architecture match SQL Assistant. Check whether the DSN belongs to the current Windows user.
Login is rejectedConfirm the username, configured authentication mechanism and account status with your DBA. Keep passwords out of saved SQL and screenshots.
Connection times outCheck hostname resolution, VPN access and the required network route. A working desktop client still needs access to the database endpoint.
ODBC works but .NET does notReview the .NET provider installation and its separate data-source definition. ODBC settings are not automatically reused.
Dates display differentlyCompare the typed DATE with explicit TO_CHAR output and check provider/client display settings.
Exported columns are misalignedCheck delimiter, text qualification and embedded commas or line breaks with a CSV parser.
Rows appear to be missingCheck client result limits, cancellation and the query predicate. Verify counts against the same data snapshot; do not count text lines if fields can contain newlines.

SQL Assistant alternatives

Use SQL Assistant for an approved Windows desktop workflow. Teradata Studio provides another Teradata client option; check its supported platform and runtime requirements. BTEQ suits scriptable terminal work, while TPT is designed for data movement. These tools serve different purposes, so compare the tasks your team actually needs to perform.

Official references

The procedures above are based on the SQL Assistant for Windows connection documentation and Exporting Results. The linked guide is the October 2018 edition; verify version-specific menu details and support requirements against your installed release.

Building or improving a data pipeline?

Discuss ingestion, transformations, orchestration, quality checks and operational handover.

Explore data engineering services

Teradata Query Performance Tuning: The DWHPro Guide book cover

Get the complete Teradata tuning book, free

Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis

206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.

Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.

About the free book

Follow DWHPro in Google to see our articles more often in Search.

Leave a Comment

Teradata Query Performance Tuning: The DWHPro Guide book cover

Get the complete Teradata tuning book, free

Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis

206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.

Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.

About the free book

Protected by Security by CleanTalk and CleanTalk Anti-Spam