Vendors.config - SQL Assistant

Teradata SQL Assistant for Microsoft Windows User Guide

SQL Assistant
Release Number
English (United States)
Last Update
Product Category
Teradata Tools and Utilities

This file describes how the application should work with different vendor databases. In general this file should only be modified if a customer wishes to support a new database that SQL Assistant does not currently support, or if the database settings cause SQL Assistant’s default settings to work incorrectly with that database.

The application never writes to this file.


Table 53: Properties Described by the Vendors.config File  




The first 5 characters of the DbmsName string returned by ODBC.

For an ‘unknown’ vendor database this string appears in parens after the Data Source name in the Database Explorer Tree. It must be in uppercase.


The name to be displayed after the Data Source name in the Explorer Tree


The SQL dialect used by this vendor

This string is used to load the Language and Syntax Example files. It is normally the same as Name, however there are exceptions. For example, Greenplum uses PostgreSQL.


A numeric value used for database vendors that are known to SQL Assistant

Use 0 for unknown, or a value >40 for new data sources.


The name of the catalog database. e.g. DBC for Teradata

This database is added to the Database Explorer Tree. The default is empty (No catalog).


Specifies whether the DBMS supports multiple Databases

The default is true.


Specifies whether /* ... */ style comments must be removed from statements before they are submitted to the database

The default is false.


Specifies whether object names must be in upper case for use in catalog functions

The default is false.


Specifies whether a User can contain Tables, and so forth.

The default is false.


Uses the CatalogName parameter in ODBC catalog functions rather than the SchemaName parameter to specify the object container

The default is false.

Note: If the DBType is set to zero (Unknown), this value is overridden by the Use alternate schema... option on the DB Tree tab of Options.


Specifies whether object names should be prefixed by their container (Database) name when SQL Assistant generates SQL statements

The default is true.


The SQL used to return a table definition

The default is empty.


The SQL used to return a view definition

The default is empty.


The SQL used to return a procedure or function definition

The default is empty.


The SQL used to change the user’s password

The default is empty.

The Change Password menu is not available unless this is provided.


Specifies whether the SQL used for a Show Definition function includes both prefix and body values. If the value is true then the SQL for all ShowXxxx properties must return 2 columns. The displayed DDL is the concatenation of these 2 values. The default is false.

Some of the strings used in this file can contain variables for which object names, or types, need to be substituted. The recognized variable names are described below:


In some cases, database compatibility might require changes to the vendor specific language file. For example, SQL Server allows the administrator to define the characters used to delimit an object name. By default the system uses the characters ‘[‘ and ‘]’ but it can be changed to use double quotes. In this case the SqlServer.lng file would have to be changed to match.