Category: Database Connectors
Introduction
This document is created to help setup a mindzieDataDesigner connector to Teradata database. The mindzieDataDesigner is the ETL tool used by mindzieStudio to convert database tables to process mining event logs. The purpose of this document is to help creating the connection string and opening ports on the firewall if required.
Overview
The Teradata connector provides high-performance connectivity to Teradata systems for enterprise-scale analytics and process mining scenarios.
System Requirements
- Database System: Teradata Database 16.0 or later (17.x recommended)
- Architecture: Massively Parallel Processing (MPP)
- Platform Support: Teradata systems on various platforms
- Dependencies: Teradata .NET Data Provider
- Network: Teradata Gateway or direct network connectivity
Connection String Format
Basic Format
Data Source=hostname;User ID=username;Password=password;Database=database_name;
Connection Parameters
| Parameter | Description | Required | Example |
|---|---|---|---|
Data Source |
Teradata server name | Yes | teradata.company.com |
User ID |
Username | Yes | mindzie_user |
Password |
Password | Yes | SecurePassword123 |
Database |
Default database | No | ANALYTICS_DB |
Connection Timeout |
Connection timeout | No | 60 |
Command Timeout |
Query timeout | No | 1800 |
Session Mode |
Session mode | No | Teradata |
Logmech |
Authentication mechanism | No | TD2 |
Connection Examples
Standard Connection
Data Source=teradata-prod.company.com;User ID=mindzie_user;Password=SecurePassword123;Database=PROCESS_ANALYTICS;
Connection with Extended Timeout
Data Source=teradata.company.com;User ID=analyst;Password=password;Database=DW;Connection Timeout=120;Command Timeout=3600;
LDAP Authentication
Data Source=teradata-server;User ID=domain\username;Password=password;Database=ANALYTICS;Logmech=LDAP;
Multi-Statement Connection
Data Source=teradata.company.com;User ID=user;Password=password;Database=DB;Session Mode=Teradata;
Troubleshooting
Common Issues
"Login failed" Error
- Verify username and password
- Check authentication mechanism (Logmech)
- Ensure user account is not locked
- Validate network connectivity to Teradata system
"Database not found" Error
- Verify database name exists
- Check user permissions for database access
- Ensure proper database qualification in queries
"Query timeout" Error
- Increase Command Timeout value
- Optimize query performance
- Check for resource constraints
- Monitor workload management settings
"Connection timeout" Error
- Increase Connection Timeout value
- Check network connectivity and latency
- Verify Teradata system availability
- Review firewall and network configuration
mindzie Server Access: For enhanced security, you can configure your firewall to only allow connections from mindzie servers by whitelisting specific IP addresses. Contact mindzie support to obtain the current IP addresses for the mindzie servers you are using.
Related Information
- Official Documentation: Teradata Documentation
- Teradata .NET Provider: .NET Data Provider Guide
- SQL Reference: Teradata SQL Reference
- Performance Guide: Teradata Performance Tuning
💡 Tip: Leverage Teradata's columnar capabilities and temporal features for efficient time-based process mining analysis on large enterprise datasets.