Teradata (beta)

Connection overview. Requires: CLI v0.62.0 and Data Collector v15555 or newer

Integrating Monte Carlo with Teradata allows you to monitor your data assets through custom SQL monitors, which can be created in either the UI wizard and/or programmatically via monitors as code (API/SDK too). These monitors can be used to generate notifications (incidents) to relevant stakeholders and circuit break pipelines.

Integration Setup

To connect Monte Carlo to a Teradata database, follow these steps:

  1. Enable network connectivity between the database and Monte Carlo's data collector.
  2. Create a read-only service account with the appropriate permissions on your database.
  3. Provide service account credentials to Monte Carlo (requires Using the CLI).

1. Enable network connectivity

Follow the Network Connectivity guide to IP Allowlist or VPC peer to provide access to Teradata.

2. Create a read-only service account



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

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>
SPOOL = 10000000 BYTES;

-- Grants SELECT access on required metadata tables
GRANT SELECT ON DBC.DatabasesV TO montecarlo;
GRANT SELECT ON DBC.TablesV 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

3. Provide service account credentials to Monte Carlo

  1. Please follow this guide to install and configure the CLI.
  2. Please use the command montecarlo integrations add-teradata to connect. For reference, see help here.
montecarlo integrations add-teradata \
--host example.fake.teradata.com \
--port 80 \
--user montecarlo \
--password -1 \
--name teradata

Monitor Support

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

CategoryMonitor TypeSupport
Automated Anomaly DetectionFreshness
Automated Anomaly DetectionVolume
Automated MonitoringSchema Changes
Opt-in MonitorSQL Rule:white-check-mark:
Opt-in MonitorComparison Rule:white-check-mark:
Opt-in MonitorField Quality Rule
Opt-in MonitorFreshness Rule
Opt-in MonitorVolume Rule
Opt-in MonitorVolume Anomaly Detection:white-check-mark:
Opt-in MonitorField Health Monitor
Opt-in MonitorDimension Tracking
Opt-in MonitorJSON Schema Changes


What hosting solutions are supported?
This integration supports any instance that is reachable from the AWS cloud (e.g. AWS hosted, site-to-site VPN with AWS, publicly accessible, etc). Please see the networking docs for more detail.

How do I fix No more spool space in montecarlo. error?
Depending on the size of your tables, 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;