Teradata (beta)

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 the service account credentials in your Monte Carlo onboarding wizard to validate and complete the integration.

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

πŸ“˜

Prerequisites

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>
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.ColumnxVX 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;

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:white-check-mark:
Automated MonitoringSchema Changes:white-check-mark:
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:white-check-mark:
Opt-in MonitorVolume Anomaly Detection:white-check-mark:
Opt-in MonitorField Health Monitor
Opt-in MonitorDimension Tracking
Opt-in MonitorJSON Schema Changes

FAQs

What hosting solutions are supported?
This integration supports any instance that is reachable from the internet, or through an Agent .

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 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;