diff --git a/quickstarts/create-applications/teradata-connector-mule4-reference.md b/quickstarts/create-applications/teradata-connector-mule4-reference.md
index 6662636255..35fb21b306 100644
--- a/quickstarts/create-applications/teradata-connector-mule4-reference.md
+++ b/quickstarts/create-applications/teradata-connector-mule4-reference.md
@@ -1,13 +1,14 @@
---
sidebar_position: 6
-author: Tan Nguyen
-email: tan.nguyen@teradata.com
-page_last_update: February 10th, 2023
+author: Tan Nguyen, Vidhan Bhonsle
+email: developer.relations@teradata.com
+page_last_update: June 22nd, 2026
description: Technical Reference for Teradata Connector for MuleSoft's Anypoint Studio.
-keywords: [data warehouses, compute storage separation, teradata, vantage, cloud data platform, object storage, business intelligence, enterprise analytics, mule, mulesoft, teradata connector, anypoint studio.]
+keywords: [data warehouses, compute storage separation, teradata, teradata database, cloud data platform, object storage, business intelligence, enterprise analytics, mule, mulesoft, teradata connector, anypoint studio.]
---
# Teradata Connector Reference - Mule 4
+
## Configurations
---
@@ -21,7 +22,7 @@ Use these parameters to configure the default configuration.
|-----------------------|------------|-----------------|-------------------|--------------|
| **Name** | String | The name for this configuration. Connectors reference the configuration with this name. | | x |
| **Connection** |
[Data Source Reference Connection](#data-source-reference-connection) [Teradata Connection](#teradata-connection) | The connection types to provide to this configuration. | | x
-| **Expiration Policy** | [Expiration Policy](#redelivery-policy) | Configures the minimum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration. This does not mean that the platform expires the instance at the exact moment that it becomes eligible. Mule purges the instances as appropriate. |
+| **Expiration Policy** | [Expiration Policy](#expiration-policy) | Configures the minimum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration. This does not mean that the platform expires the instance at the exact moment that it becomes eligible. Mule purges the instances as appropriate. |
#### Connection Types
@@ -49,7 +50,7 @@ When you use a _provider's custom type_ in a Data Source Reference Connection, d
|-----------------------|------------|-----------------|-------------------|--------------|
| **Pooling Profile**| [Pooling Profile](#pooling-profile) | Provides a way to configure database connection pooling | |
| **Column Types**| Array of [Column Type](#column-type) | Specifies non-standard column types | |
-| **Transaction Isolation a**| Enumeration, one of:
NONE
READ_COMMITTED
READ_UNCOMMITTED
REPEATABLE_READ
SERIALIZABLE
NOT_CONFIGURED | The transaction isolation level to set on the driver when connecting the database | `NOT_CONFIGURED` |
+| **Transaction Isolation**| Enumeration, one of:
NONE
READ_COMMITTED
READ_UNCOMMITTED
REPEATABLE_READ
SERIALIZABLE
NOT_CONFIGURED | The transaction isolation level to set on the driver when connecting the database | `NOT_CONFIGURED` |
| **Use XA Transactions**| Boolean | Indicates whether or not the created datasource must support XA transactions | `false` |
| **URL** | String | JDBC URL to use to connect to the database | | x
| **User** | String | Database username | |
@@ -96,7 +97,7 @@ This operation allows delete operations to execute at various times using differ
| **Transactional Action**| Enumeration, one of:
ALWAYS_JOIN
JOIN_IF_POSSIBLE
NOT_SUPPORTED | The type of joining action that operations can take regarding transactions | `JOIN_IF_POSSIBLE` |
| **Query Timeout** | Number | Indicates the minimum amount of time before the JDBC driver attempts to cancel a running statement. By default, no timeout is used. | `0` |
| **Query Timeout Unit** | Enumeration, one of:
NANOSECONDS
MICROSECONDS
MILLISECONDS
SECONDS
MINUTES
HOURS
DAYS | A time unit that qualifies the `#queryTimeout`. Values specified in nanoseconds, microseconds, or milliseconds are rounded to seconds. | `SECONDS` |
-| Fetch Size a| Number | Indicates how many rows to fetch from the database when rows are read from a ResultSet. This property is required when streaming is true, in which case a default value of `10` is used. | |
+| **Fetch Size** | Number | Indicates how many rows to fetch from the database when rows are read from a ResultSet. This property is required when streaming is true, in which case a default value of `10` is used. | |
| **Max Rows** | Number | Sets the limit for the maximum number of rows that any ResultSet object generated by this message processor can contain for the given number. If the limit is exceeded, the excess rows are silently dropped. | |
| **SQL Query Text** | String | The text of the SQL query to execute | | x
| **Parameter Types** | Array of [Parameter Type](#parameter-type) | This parameter allows you to optionally specify the type of one or more of the parameters in the query. If a value is provided, you're not required to reference all of the parameters; but you cannot reference a parameter that is not present in the input values. | |
@@ -181,7 +182,7 @@ This operation allows updates to execute at various times using different parame
| **Configuration** | String | The name of the configuration to use | | x
| **Input Parameters** | Array of Object | Specifies a list of maps, which contain the parameter names as keys and the value the parameter is bound to, and in which every list item represents a row to insert. | `#[payload]` |
| **Transactional Action** | Enumeration, one of:
ALWAYS_JOIN
JOIN_IF_POSSIBLE
NOT_SUPPORTED | The type of joining action that operations can take regarding transactions. | JOIN_IF_POSSIBLE |
-| **Query Timeout** Number | Indicates the minimum amount of time before the JDBC driver attempts to cancel a running statement. By default, no timeout is used. | `0` |
+| **Query Timeout** | Number | Indicates the minimum amount of time before the JDBC driver attempts to cancel a running statement. By default, no timeout is used. | `0` |
| **Query Timeout Unit** | Enumeration, one of:
NANOSECONDS
MICROSECONDS
MILLISECONDS
SECONDS
MINUTES
HOURS
DAYS | A time unit that qualifies the `#queryTimeout`. Values specified in nanoseconds, microseconds, or milliseconds are rounded to seconds. | `SECONDS` |
| **Fetch Size** | Number | Indicates how many rows to fetch from the database when rows are read from a ResultSet. | 10 |
| **Max Rows** | Number | Sets the limit for the maximum number of rows that any ResultSet object generated by this message processor can contain for the given number. If the limit is exceeded, the excess rows are silently dropped. | |
@@ -265,7 +266,7 @@ This operation allows execution of DDL queries against a database.
| **SQL Query Text** | String | The text of the SQL query to execute | | x
| **Transactional Action** | Enumeration, one of:
ALWAYS_JOIN
JOIN_IF_POSSIBLE
NOT_SUPPORTED | The type of joining action that operations can take regarding transactions | `JOIN_IF_POSSIBLE` |
| **Query Timeout** | Number | Indicates the minimum amount of time before the JDBC driver attempts to cancel a running statement. By default, no timeout is used. | `0` |
-| **Query Timeout Unit** | Enumeration, one of:
NANOSECONDS
MICROSECONDS
MILLISECONDS
SECONDS
MINUTES
HOURS DAYS | A time unit that qualifies the `#queryTimeout`. Values specified in nanoseconds, microseconds, or milliseconds are rounded to seconds. | `SECONDS` |
+| **Query Timeout Unit** | Enumeration, one of:
NANOSECONDS
MICROSECONDS
MILLISECONDS
SECONDS
MINUTES
HOURS
DAYS | A time unit that qualifies the `#queryTimeout`. Values specified in nanoseconds, microseconds, or milliseconds are rounded to seconds. | `SECONDS` |
| **Fetch Size** | Number | Indicates how many rows to fetch from the database when rows are read from a ResultSet. | 10 |
| **Max Rows** | Number | Sets the limit for the maximum number of rows that any ResultSet object generated by this message processor can contain for the given number. If the limit is exceeded, the excess rows are silently dropped. | |
| **Target Variable** | String | The name of a variable to store the operation's output | |
@@ -289,7 +290,7 @@ This operation allows execution of DDL queries against a database.
* DB:BAD_SQL_SYNTAX
-[[executeScript]]
+
### Execute Script
``
@@ -301,7 +302,7 @@ This operation executes an SQL script in a single database statement. The script
| **Name** | **Type** | **Description** | **Default Value** | **Required** |
|------|------|-------------|---------------|----------|
| **Configuration** | String | The name of the configuration to use | | x
-| **Transactional Action** | Enumeration, one of:
ALWAYS_JOIN JOIN_IF_POSSIBLE NOT_SUPPORTED | The type of joining action that operations can take for transactions. | `JOIN_IF_POSSIBLE` |
+| **Transactional Action** | Enumeration, one of:
ALWAYS_JOIN
JOIN_IF_POSSIBLE
NOT_SUPPORTED | The type of joining action that operations can take for transactions. | `JOIN_IF_POSSIBLE` |
| **SQL Query Text** | String | The text of the SQL query to execute | |
| **Script Path** | String | Specifies the location of a file to load. The file can point to a resource on the classpath, or on a disk. | |
| **Query Timeout** | Number | Indicates the minimum amount of time before the JDBC driver attempts to cancel a running statement. By default, no timeout is used. | `0` |
@@ -341,7 +342,7 @@ This operation inserts data into a database.
| **Name** | **Type** | **Description** | **Default Value** | **Required** |
|------|------|-------------|---------------|----------|
| **Configuration** | String | The name of the configuration to use | | x
-| Transactional Action a| Enumeration, one of:
ALWAYS_JOIN
JOIN_IF_POSSIBLE
NOT_SUPPORTED | The type of joining action that operations can take regarding transactions | `JOIN_IF_POSSIBLE` |
+| **Transactional Action** | Enumeration, one of:
ALWAYS_JOIN
JOIN_IF_POSSIBLE
NOT_SUPPORTED | The type of joining action that operations can take regarding transactions | `JOIN_IF_POSSIBLE` |
| **Query Timeout** | Number | Indicates the minimum amount of time before the JDBC driver attempts to cancel a running statement. By default, no timeout is used. | `0` |
| **Query Timeout Unit** | Enumeration, one of:
NANOSECONDS
MICROSECONDS
MILLISECONDS
SECONDS
MINUTES
HOURS
DAYS | A time unit that qualifies the `#queryTimeout`. Values specified in nanoseconds, microseconds, or milliseconds are rounded to seconds. | `SECONDS` |
| **Fetch Size** | Number | Indicates how many rows to fetch from the database when rows are read from a ResultSet. | 10 |
@@ -382,18 +383,18 @@ This operation queries data from a database. To prevent loading all the results
| **Name** | **Type** | **Description** | **Default Value** | **Required** |
|------|------|-------------|---------------|----------|
| **Configuration** | String | The name of the configuration to use | | x
-| **Transactional Action** | Enumeration, one of:
ALWAYS_JOIN
JOIN_IF_POSSIBLE
NOT_SUPPORTED | The type of joining action that operations can take regarding transactions | `JOIN_IF_POSSIBLE` | |
-**Streaming Strategy** | [Repeatable In Memory Iterable](#repeatable-in-memory-iterable)
[Repeatable File Store Iterable](#repeatable-file-store-iterable)
non-repeatable-iterable | Configure to use repeatable streams | |
-| **Query Timeout** a| Number | Indicates the minimum amount of time before the JDBC driver attempts to cancel a running statement. By default, no timeout is used. | `0` |
-| **Query Timeout Unit** a| Enumeration, one of:
NANOSECONDS
MICROSECONDS
MILLISECONDS
SECONDS
MINUTES
HOURS
DAYS | A time unit that qualifies the `#queryTimeout`. Values specified in nanoseconds, microseconds, or milliseconds are rounded to seconds. | `SECONDS` |
-| **Fetch Size** a| Number | Indicates how many rows to fetch from the database when rows are read from a ResultSet. | 10 |
-| **Max Rows** a| Number | Sets the limit for the maximum number of rows that any ResultSet object generated by this message processor can contain for the given number. If the limit is exceeded, the excess rows are silently dropped. | |
-| **SQL Query Text** a| String | The text of the SQL query to execute | | x
-| **Parameter Types** a| Array of [Parameter Type](#parameter-type) | Allows you to optionally specify the type of one or more of the parameters in the query. If provided, you're not required to reference all of the parameters; but you cannot reference a parameter that is not present in the input values. | |
-| **Input Parameters** a| Object | A map in which keys are the name of an input parameter to be set on the JDBC prepared statement. Each parameter should be referenced in the SQL text using a colon prefix (for example: where id = :myParamName). The map's values will contain the actual assignation for each parameter. | |
+| **Transactional Action** | Enumeration, one of:
ALWAYS_JOIN
JOIN_IF_POSSIBLE
NOT_SUPPORTED | The type of joining action that operations can take regarding transactions | `JOIN_IF_POSSIBLE` |
+| **Streaming Strategy** | [Repeatable In Memory Iterable](#repeatable-in-memory-iterable)
[Repeatable File Store Iterable](#repeatable-file-store-iterable)
non-repeatable-iterable | Configure to use repeatable streams | |
+| **Query Timeout** | Number | Indicates the minimum amount of time before the JDBC driver attempts to cancel a running statement. By default, no timeout is used. | `0` |
+| **Query Timeout Unit** | Enumeration, one of:
NANOSECONDS
MICROSECONDS
MILLISECONDS
SECONDS
MINUTES
HOURS
DAYS | A time unit that qualifies the `#queryTimeout`. Values specified in nanoseconds, microseconds, or milliseconds are rounded to seconds. | `SECONDS` |
+| **Fetch Size** | Number | Indicates how many rows to fetch from the database when rows are read from a ResultSet. | 10 |
+| **Max Rows** | Number | Sets the limit for the maximum number of rows that any ResultSet object generated by this message processor can contain for the given number. If the limit is exceeded, the excess rows are silently dropped. | |
+| **SQL Query Text** | String | The text of the SQL query to execute | | x
+| **Parameter Types** | Array of [Parameter Type](#parameter-type) | Allows you to optionally specify the type of one or more of the parameters in the query. If provided, you're not required to reference all of the parameters; but you cannot reference a parameter that is not present in the input values. | |
+| **Input Parameters** | Object | A map in which keys are the name of an input parameter to be set on the JDBC prepared statement. Each parameter should be referenced in the SQL text using a colon prefix (for example: where id = :myParamName). The map's values will contain the actual assignation for each parameter. | |
| **Target Variable** | String | The name of a variable to store the operation's output. | |
| **Target Value** | String | An expression to evaluate against the operation's output and store the expression outcome in the target variable | `#[payload]` |
-| **Reconnection Strategy** | [Reconnect](#reconnect)
[Reconnect Forever](#reconnect-forever) | A retry strategy in case of connectivity errors. | ||
+| **Reconnection Strategy** | [Reconnect](#reconnect)
[Reconnect Forever](#reconnect-forever) | A retry strategy in case of connectivity errors. | |
|Type |Array of Object|
@@ -434,8 +435,8 @@ This operation selects a single data record from a database. If you provide an S
| **Configuration** | String | The name of the configuration to use | | x
| **Transactional Action** | Enumeration, one of:
ALWAYS_JOIN
JOIN_IF_POSSIBLE
NOT_SUPPORTED | The type of join action that operations can take regarding transactions | `JOIN_IF_POSSIBLE` |
| **Streaming Strategy** | [Repeatable In Memory Iterable](#repeatable-in-memory-iterable)
[Repeatable File Store Iterable](#repeatable-file-store-iterable)
non-repeatable-iterable | Configure to use repeatable streams | |
-| Query Timeout a| Number | Indicates the minimum amount of time before the JDBC driver attempts to cancel a running statement. By default, no timeout is used. | `0` |
-| Query Timeout Unit a| Enumeration, one of:
NANOSECONDS MICROSECONDS
MILLISECONDS
SECONDS
MINUTES
HOURS
DAYS | A time unit that qualifies the `#queryTimeout`. Values specified in nanoseconds, microseconds, or milliseconds are rounded to seconds. | `SECONDS` |
+| **Query Timeout** | Number | Indicates the minimum amount of time before the JDBC driver attempts to cancel a running statement. By default, no timeout is used. | `0` |
+| **Query Timeout Unit** | Enumeration, one of:
NANOSECONDS
MICROSECONDS
MILLISECONDS
SECONDS
MINUTES
HOURS
DAYS | A time unit that qualifies the `#queryTimeout`. Values specified in nanoseconds, microseconds, or milliseconds are rounded to seconds. | `SECONDS` |
| **Fetch Size** | Number | Indicates how many rows to fetch from the database when rows are read from a ResultSet. | 10 |
| **Max Rows** | Number | The maximum number of rows that any ResultSet object generated by this message processor can contain. If the limit is exceeded, the excess rows are silently dropped. | |
| **SQL Query Text** | String | The text of the SQL query to execute | | x
@@ -443,7 +444,7 @@ This operation selects a single data record from a database. If you provide an S
| **Input Parameters** | Object | A map in which keys are the name of an input parameter to be set on the JDBC prepared statement. Each parameter should be referenced in the SQL text using a colon prefix (for example: where id = :myParamName). The map's values will contain the actual assignation for each parameter. | |
| **Target Variable** | String | Name of the variable in which to store the operation's output | |
| **Target Value** | String | Expression that evaluates the operation's output. The expression outcome is stored in the target variable. | `#[payload]` |
-| **Reconnection Strategy** | [Reconnect](#reconnect)
[Reconnect Forever](#reconnect-forever) | A retry strategy in case of connectivity errors. | ||
+| **Reconnection Strategy** | [Reconnect](#reconnect)
[Reconnect Forever](#reconnect-forever) | A retry strategy in case of connectivity errors. | |
#### Output
|Type | Object|
|----|-----|
@@ -472,9 +473,9 @@ Invokes a stored procedure on the database. When the stored procedure returns o
| **Name** | **Type** | **Description** | **Default Value** | **Required** |
|------|------|-------------|---------------|----------|
| **Configuration** | String | The name of the configuration to use. | | x
-| **Transactional Action** | Enumeration, one of:
ALWAYS_JOIN
JOIN_IF_POSSIBLE
NOT_SUPPORTED | The type of joining action that operations can take regarding transactions. | JOIN_IF_POSSIBLE ||
-**Streaming Strategy** | [Repeatable In Memory Iterable](#repeatable-in-memory-iterable)
[Repeatable File Store Iterable](#repeatable-file-store-iterable)
non-repeatable-iterable | Configure to use repeatable streams | |
-| Query Timeout a| Number | Indicates the minimum amount of time before the JDBC driver attempts to cancel a running statement. No timeout is used by default. | 0 |
+| **Transactional Action** | Enumeration, one of:
ALWAYS_JOIN
JOIN_IF_POSSIBLE
NOT_SUPPORTED | The type of joining action that operations can take regarding transactions. | JOIN_IF_POSSIBLE |
+| **Streaming Strategy** | [Repeatable In Memory Iterable](#repeatable-in-memory-iterable)
[Repeatable File Store Iterable](#repeatable-file-store-iterable)
non-repeatable-iterable | Configure to use repeatable streams | |
+| **Query Timeout** | Number | Indicates the minimum amount of time before the JDBC driver attempts to cancel a running statement. No timeout is used by default. | 0 |
| **Query Timeout Unit** | Enumeration, one of:
NANOSECONDS
MICROSECONDS
MILLISECONDS
SECONDS
MINUTES
HOURS
DAYS | A time unit that qualifies the `#queryTimeout`. Values specified in nanoseconds, microseconds, or milliseconds are rounded to seconds. | `SECONDS` |
| **Fetch Size** | Number | Indicates how many rows to fetch from the database when rows are read from a resultSet. This property is required when streaming is true; in that case a default value (10) is used. | |
| **Max Rows** | Number | Sets the limit for the maximum number of rows that any ResultSet object generated by this message processor can contain for the given number. If the limit is exceeded, the excess rows are silently dropped. | |
@@ -488,7 +489,7 @@ Invokes a stored procedure on the database. When the stored procedure returns o
| **Auto Generated Keys Column Names** | Array of String | List of column names that indicates which auto-generated keys should be made available for retrieval. | |
| **Target Variable** | String | The name of a variable to store the operation's output. | |
| **Target Value** | String | An expression to evaluate against the operation's output and store the expression outcome in the target variable | `#[payload]` |
-| **Reconnection Strategy** | [Reconnect](#reconnect)
[Reconnect Forever](#reconnect-forever) | A retry strategy in case of connectivity errors | ||
+| **Reconnection Strategy** | [Reconnect](#reconnect)
[Reconnect Forever](#reconnect-forever) | A retry strategy in case of connectivity errors | |
#### Output
|Type |Object|
@@ -526,8 +527,7 @@ Updates data in a database.
| **Configuration** | String | The name of the configuration to use | | x |
| **Transactional Action** | Enumeration, one of:
ALWAYS_JOIN
JOIN_IF_POSSIBLE
NOT_SUPPORTED | The type of joining action that operations can take for transactions | `JOIN_IF_POSSIBLE` |
| **Query Timeout** | Number | Indicates the minimum amount of time before the JDBC driver attempts to cancel a running statement. By default, no timeout is used. | `0` |
-| **Query Timeout Unit** | Enumeration, one of:
NANOSECONDS
MICROSECONDS
MILLISECONDS
SECONDS
MINUTES
HOURS
-** DAYS | A time unit that qualifies the `#queryTimeout`. Values specified in nanoseconds, microseconds, or milliseconds are rounded to seconds. | `SECONDS` |
+| **Query Timeout Unit** | Enumeration, one of:
NANOSECONDS
MICROSECONDS
MILLISECONDS
SECONDS
MINUTES
HOURS
DAYS | A time unit that qualifies the `#queryTimeout`. Values specified in nanoseconds, microseconds, or milliseconds are rounded to seconds. | `SECONDS` |
| **Fetch Size** | Number | Indicates how many rows to fetch from the database when rows are read from a ResultSet. | 10 |
| **Max Rows** | Number | Sets the limit for the maximum number of rows that any ResultSet object generated by this message processor can contain for the given number. If the limit is exceeded, the excess rows are silently dropped. | |
| **SQL Query Text** | String | The text of the SQL query to execute | | x
@@ -604,9 +604,9 @@ This operation does not support streaming, meaning that there is no need to perf
| **Max Pool Size** | Number | Maximum number of connections a pool maintains at any given time | `5` |
| **Min Pool Size** | Number | Minimum number of connections a pool maintains at any given time | `0` |
| **Acquire Increment** | Number | Determines how many connections at a time to try to acquire when the pool is exhausted | `1` |
-| **Prepared Statement Cache Size** Number | Determines how many statements are cached per pooled connection. Setting this to zero disables statement caching. | `5` |
+| **Prepared Statement Cache Size** | Number | Determines how many statements are cached per pooled connection. Setting this to zero disables statement caching. | `5` |
| **Max Wait** | Number | The amount of time a client trying to obtain a connection waits for it to be acquired when the pool is exhausted. Setting this value to zero (default) means wait indefinitely. This is equivalent to `checkoutTimeout` and cannot be overridden in additional-properties. | `0` |
-| **Max Wait Unit** | Enumeration, one of:
NANOSECONDS
MICROSECONDS
MILLISECONDS
SECONDS
MINUTES
HOURS
DAYS | A #maxWait. | SECONDS |
+| **Max Wait Unit** | Enumeration, one of:
NANOSECONDS
MICROSECONDS
MILLISECONDS
SECONDS
MINUTES
HOURS
DAYS | A time unit that qualifies the maxWait attribute. | SECONDS |
| **Max Idle Time** | Number | Determines how many seconds a connection can remain pooled but unused before being discarded. Setting this value to zero (default) means idle connections never expire. | `0` |
| **Additional Properties** | Object | A map in which keys are the name of a pooling profile configuration property. Does not support the use of expressions. These properties cannot be used to override any of the previously specified properties (like Max Pool Size or Min Pool Size), the main property prevails if an attempt is made to override it. The map's values contain the actual assignation for each parameter. | |
| **Max Statement** | Number | Defines the total number PreparedStatements a DataSource will cache. The pool destroys the least-recently-used PreparedStatement when it reaches the specified limit. When set to `0`, statement caching is turned off | |
@@ -795,4 +795,4 @@ This operation does not support streaming, meaning that there is no need to perf
## See Also
-- [MuleSoft Help Center](https://help.mulesoft.com)
\ No newline at end of file
+- [MuleSoft Help Center](https://help.mulesoft.com)
diff --git a/quickstarts/create-applications/teradata-connector-mule4.md b/quickstarts/create-applications/teradata-connector-mule4.md
index f1c5d0a8c9..e5c39abdb9 100644
--- a/quickstarts/create-applications/teradata-connector-mule4.md
+++ b/quickstarts/create-applications/teradata-connector-mule4.md
@@ -1,17 +1,17 @@
---
sidebar_position: 7
-author: Tan Nguyen
-email: tan.nguyen@teradata.com
-page_last_update: February 10th, 2023
+author: Tan Nguyen, Vidhan Bhonsle
+email: developer.relations@teradata.com
+page_last_update: June 22nd, 2026
description: Use Teradata Connector for MuleSoft's Anypoint Studio.
-keywords: [data warehouses, compute storage separation, teradata, vantage, cloud data platform, object storage, business intelligence, enterprise analytics, mule, mulesoft, teradata connector, anypoint studio.]
+keywords: [data warehouses, compute storage separation, teradata, teradata database, teradata connector, object storage, business intelligence, enterprise analytics, mule, mulesoft, anypoint studio.]
---
import TrialDocsNote from '../_partials/teradata_trial.mdx'
# Teradata Connector - Mule 4
-Anypoint Connector for Teradata (Teradata Connector) establishes communication between your Mule app and a Teradata Vantage database, enabling you to connect with your Teradata Vantage instance to load data and run SQL queries in Teradata Vantage tables.
+Anypoint Connector for Teradata (Teradata Connector) establishes communication between your Mule app and a Teradata database, enabling you to connect with your Teradata instance to load data and run SQL queries in Teradata tables.
Reference: [Teradata Connector Reference](./teradata-connector-mule4-reference.md)
@@ -20,7 +20,7 @@ Reference: [Teradata Connector Reference](./teradata-connector-mule4-reference.m
To use this connector, you must be familiar with:
-- Teradata Vantage SQL
+- Teradata SQL
- Anypoint Connectors
- Mule runtime engine (Mule)
- Elements and global elements in a Mule flow
@@ -29,7 +29,7 @@ To use this connector, you must be familiar with:
Before creating an app, you must have:
- Anypoint Studio version 7.5 or later
-- Credentials to access the Teradata Vantage target resource
+- Credentials to access the Teradata target resource
@@ -53,7 +53,7 @@ The Teradata Connector supports:
After you complete the prerequisites, you can try the examples and configure the connector using Anypoint Studio.
-- [Query Teradata Vantage from a Mule service](https://quickstarts.teradata.com/mule.jdbc.example.html)
+- [Query Teradata from a Mule service](https://quickstarts.teradata.com/mule.jdbc.example.html)
- [Using Anypoint Studio to Configure Teradata Connector](./examples-configuration.md)
## See Also
diff --git a/quickstarts/introduction/teradata-engine-architecture-and-concepts.md b/quickstarts/introduction/teradata-engine-architecture-and-concepts.md
index 9d3c0a9c50..559a9a6900 100644
--- a/quickstarts/introduction/teradata-engine-architecture-and-concepts.md
+++ b/quickstarts/introduction/teradata-engine-architecture-and-concepts.md
@@ -14,11 +14,11 @@ keywords: [data warehouses, teradata engine architecture, teradata, teradata dat
### Overview
-This article explains the underlying concepts of Teradata engine architecture. All editions of Teradata, including the Primary Cluster in VantageCloud Lake, use the same engine.
+This article explains the underlying concepts of Teradata engine architecture. All editions of Teradata use the same engine.
Teradata's architecture is based on a Massively Parallel Processing (MPP), shared-nothing architecture that enables high-performance data processing and analytics. MPP distributes workloads across multiple vprocs, or virtual processors. The virtual processor responsible for query processing is commonly referred to as Access Module Processor (AMP). Each AMP is isolated from other AMPs, and processes queries in parallel, allowing Teradata to process large volumes of data rapidly.
-The major architectural components of the Teradata engine include the Parsing Engines (PEs), BYNET, Access Module Processors (AMPs), and Virtual Disks (Vdisks). Vdisks are assigned to AMPs in enterprise platforms and in the Primary Cluster for VantageCloud Lake environments.
+The major architectural components of the Teradata engine include the Parsing Engines (PEs), BYNET, Access Module Processors (AMPs), and Virtual Disks (Vdisks). Vdisks are assigned to AMPs in enterprise platforms.

@@ -55,11 +55,6 @@ AMPs are responsible for data storage and retrieval. Each AMP is associated with
* Accounting.
* Recovery processing.
-:::note
-AMPs in VantageCore IntelliFlex, VantageCore VMware, VantageCloud Enterprise, and the Primary Cluster in the case of VantageCloud Lake, store data in a Block File System (BFS) format on Vdisks.
-AMPs in Compute Clusters and Compute Worker Nodes on VantageCloud Lake do not have BFS. They can only access data in object storage using the Object File System (OFS).
-:::
-
### Virtual Disks (Vdisks)
Virtual Disks are units of storage space owned by an AMP. Vdisks hold user data, such as rows within tables, and map to physical space on a disk.