Vista SQL Access Overview
TUDS, TAD, TERA, and TEDI all need a reliable path to your Vista SQL database. This guide covers the shared “what do we need?” checklist. Product-specific install steps live in each Installation Prerequisites article.
What you need from IT / Vista admin
- SQL Server host or instance name
- SQL Server port (if non-default)
- Database name (typically Viewpoint / related Vista databases)
- Authentication method: SQL login and password, or Windows integrated where the product supports it
- Network path from the product host to SQL Server
How each product uses SQL
- TUDS: End users do not connect to SQL directly. The TUDS-hosted Azure Bridge performs approved SQL work for Mission Control. Captains configure it in Team Settings → Connectors → Azure Bridge — no customer Windows bridge host is required.
- TAD: Installer and Excel sessions connect to SQL to install objects and download/import/update data.
- TERA: Crystal execution and Vista-aware report/parameter discovery use the configured SQL connection.
- TEDI: Settings → Database refreshes a local Vista metadata catalog used by automations.
Cloud vs on-prem
- On-prem: Product host must reach SQL on your LAN/VPN.
- Cloud: You typically need a TLS Database Endpoint or IPsec VPN first. See Cloud SQL Connectivity.
SQL accounts
For creating dedicated SQL logins in Vista (especially for TAD cloud users), follow Create SQL Account.