What is Teradata?

Teradata is a powerful relational database management system optimized for large-scale data warehousing and big data analytics. Known for its parallel processing capabilities, scalability, and advanced analytics features, it enables organizations to efficiently manage and analyze vast amounts of data. This makes it a preferred choice for enterprises seeking robust, high-performance solutions for data-driven decision-making.

Why Connect Teradata to Monte Carlo?

Integrating Monte Carlo with Teradata allows you to monitor your data and tables. Monte Carlo can detect anomalous freshness, volume and schema changes by default. With the ability to run SQL queries on your Teradata database, you can create advanced monitors to analyze the data in your tables and views. For a full list of supported monitor types see Monitor Support.

After connecting Teradata here is what you can expect to see:

Freshness:

Freshness monitors are active for Teradata tables by default. Monte Carlo's detection models will automatically train on the freshness metadata and alert on anomalies as they emerge.

Volume:

Volume is monitored by a Table monitor. Connecting the integration doesn't monitor any tables on its own: create a Table monitor and choose the databases and schemas it covers. By collecting metadata on your tables, Monte Carlo's machine learning algorithm can set automatic thresholds to alert when a table has gone too long without a change in size or when an abnormal amount of bytes are added or deleted.

Monitor & Lineage Support

Below are the monitors & lineage support for the Teradata integration today. Please reach out to your Monte Carlo representative if you have requirements for additional monitors.

Connecting to Teradata

Note: Teradata databases must be online for MC to be able to run collection processes

Now that we know the value connecting Teradata to Monte Carlo can bring, here are the necessary steps to set up the integration.

📘

Prerequisites

To create a service account, you will need admin credentials to your Teradata database.

This guide explains how to create a read-only service account for Monte Carlo in Teradata.

To review all steps necessary to integrate a data warehouse with Monte Carlo, please see here.

Create a read-only service account

Please run the SQL snippet below on your Teradata database to create a read-only service account for Monte Carlo

CREATE USER montecarlo AS
PASSWORD = <password>
PERMANENT = 1000000 BYTES
TEMPORARY = 1000000 BYTES
SPOOL = 10000000 BYTES;

-- Grants SELECT access on required metadata tables:
GRANT SELECT ON DBC.DatabasesVX TO montecarlo;
GRANT SELECT ON DBC.TablesVX TO montecarlo;
GRANT SELECT ON DBC.TableSizeVX TO montecarlo;
GRANT SELECT ON DBC.TableTextVX TO montecarlo;
GRANT SELECT ON DBC.ColumnsV TO montecarlo;
GRANT SELECT ON DBC.QryLogV TO montecarlo;
GRANT SELECT ON DBC.QryLogSQLV TO montecarlo;

-- Grants SELECT on all tables contained in <DATABASE NAME>. 
-- Run this command for each Database that contains tables you 
-- would like to create custom monitors on
GRANT SELECT ON <DATABASE NAME> TO montecarlo;

[Optional] Connect using SSL

Monte Carlo supports connecting to your Teradata database using an SSL encrypted connection. You must use the Monte Carlo CLI to configure SSL for new or existing Teradata integrations. If you do not already have the CLI installed see our CLI setup guide.

Use the following command to see a list of all required and optional parameters for onboarding a new Teradata connection:

montecarlo integrations add-teradata --help

Use the following command to see a list of all required and optional parameters for editing an existing Teradata connection:

montecarlo integrations update-teradata --help

For either command, to enable SSL encryption the following parameters need to be provided:

• Port: the SSL port, usually 443
• sslmode: Specifies the mode for connections to the database. The options are:
  • ALLOW: uses non-SSL connections.
  • PREFER: attempts to create a SSL connection and will fall back to non-SSL if the SSL connection cannot be established.
  • REQUIRE: uses only SSL connections.
  • VERIFY-CA: uses only SSL connections and verifies that the server certificate is valid and trusted.
  • VERIFY-FULL: uses only SSL connections, verifies that the server certificate is valid and trusted, and verifies that the server certificate matches the database hostname.
• ssl-ca-directory: Path to a directory on your local machine containing PEM files with public CA certificates to use for the SSL connection. This option cannot be used with ssl-ca.
• ssl-ca: Path to a PEM file on your local machine for a public CA certificate to use for the SSL connection. This option cannot be used with ssl-ca-directory.

How can I validate Monte Carlo has access to my assets?

After completing the Snowflake integration setup, your Snowflake assets should appear in the Monte Carlo Assets page between a few minutes and one hour. If you don't see your assets after this time period, you can run a validation test to troubleshoot the connection:

1. Navigate to Settings → Integrations
2. Find your Snowflake integration and click on it
3. Select the specific connection you want to test
4. Click the Test button from the connection menu

This validation test will help identify any configuration issues that might be preventing your assets from appearing.

When running the validation test, you should see all green checkmarks. If any errors are encountered, the system will provide specific steps to resolve them.

Note: Lineage can take up to 24 hours due to batching.

Providing credentials with the Terraform provider

The Terraform provider takes the same details as the wizard. montecarlo_teradata_credentials holds the connection details and the service account's password, and montecarlo_warehouse and montecarlo_connection put them on a deployment:

resource "montecarlo_warehouse" "teradata" {
  name            = "production-teradata"
  connection_type = "teradata"
  deployment_id   = var.deployment_id
}

resource "montecarlo_teradata_credentials" "teradata" {
  host = "teradata.example.com"
  port = 1025
  user = "monte_carlo"

  password_wo         = var.teradata_password
  password_wo_version = 1
}

resource "montecarlo_connection" "teradata" {
  name           = "production-teradata"
  warehouse_id   = montecarlo_warehouse.teradata.id
  credentials_id = montecarlo_teradata_credentials.teradata.id
}

deployment_id is the deployment the connection runs on: your collection agent's, or the Cloud deployment under Settings > Deployments if Monte Carlo connects from its cloud. Keep the password in a variable set from an uncommitted *.tfvars file or the environment; as a write-only argument it is never stored in the Terraform state or plan, which needs Terraform 1.11 or later. td_logmech and td_sslmode take Teradata's own values, and ssl_ca_data takes the CA certificate; omit them for the defaults. See montecarlo_teradata_credentials in the registry for every argument.

Providing credentials with Claude

With the Agent Toolkit, run /monte-carlo-onboarding connect Teradata and Claude does the Monte Carlo steps through the MCP server. The password never passes through the chat: Claude gives you the command or the Terraform, and you run it on your machine. Connecting a warehouse with the onboarding skill explains each step Claude takes.

Excluded Databases

The following system created databases are excluded from our metadata collection:

• All
• Crashdumps
• console
• DBC
• dbcmngr
• Default
• External_AP
• EXTUSER
• LockLogShredder
• mldb
• PUBLIC
• SQLJ
• Sys_Calendar
• SysAdmin
• SYSBAR
• SYSJDBC
• SYSLIB
• SYSSPATIAL
• SystemFe
• SYSUDTLIB
• SYSUIF
• tapidb
• TD_ANALYTICS_DB
• TD_SERVER_DB
• TD_SYSFNLIB
• TD_SYSGPL
• TD_SYSXML
• TDaaS_BAR
• TDaaS_DB
• TDaaS_Maint
• TDaaS_Monitor
• TDaaS_Support
• TDaaS_TDBCMgmt1
• TDaaS_TDBCMgmt2
• TDBCMgmt
• TDMaps
• TDPUSER
• TDQCD
• TDStats
• tdwm
• val
• viewpoint

FAQs

What hosting solutions are supported?
This integration supports any instance that is reachable from one of our hosting options. Please see the networking docs for more detail.

Can I use permissions on the Teradata user to control which tables Monte Carlo monitors?
Monte Carlo will query the view DBC.TablesVXwhen collecting metadata. This view will only return tables that the service account user owns or has been granted privileges on. If you do not want a table monitored by Monte Carlo, make sure the service account user has no privileges on that table. If you don't want an entire database (and its tables) monitored by Monte Carlo, remove all grants on that database to the service account user.

Alternatively you can use Monte Carlo's schema controls to control which catalogs and datasets are monitored.

How do I fixNo more spool space in montecarlo. error?
Teradata uses Spool Space as a temporary workspace to store intermediate and final result sets. This space is only used temporarily and is released when it is no longer needed or automatically at the end of the session. Depending on the number of tables being monitored, volume of query logs and quantity of custom monitors created, you might need to allocate more spool space to the service account that Monte Carlo is using. If you see this error when trying to add a Teradata connection (during the validation step) or during metadata collection, modify the user to allocate more spool space with this query:

MODIFY USER montecarlo AS
SPOOL = <new spool size> BYTES;

Do you support large view definitions?
We collect up to 32,000 characters of each view definition. If you need this limit increased, please ask Bayes.