Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

TABLE OF CONTENTS

Microsoft SQL Engine connection string

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedApr 24, 2025
  • 2 minute read

There are several connection string options available when connecting to the Microsoft SQL Engine. These options impact how the Microsoft SQL Engine interacts with the client application and allow a client to connect to different data sources.

Note: For a list of Open Database Connectivity (ODBC) connection string options that can be used to construct a DSN-less (data source name), fully-qualified connection string, refer to the website for more information on OpenAccess SDK Documentation. This section also explains the difference between a DSN-based and a DSN-less connection string.

The table below defines the AVEVA Enterprise SCADA-specific connection string options. You can append these options to a DSN-based or a DSN-less connection string when connecting to the Microsoft SQL Engine. These options are case-insensitive.

Option

Attribute

Comment

APPNAME

The name of the client application which is connecting to the Microsoft SQL Engine.

Can be used to override the client application name with a more "friendly" name.

CLIENTHOSTNAME

The host name from which the client is connecting to the Microsoft SQL Engine.

Typically used for remote clients to override the Remote Client Service (RCS) host name with the client host name, since RCS creates the connection on behalf of the client.

DEFAULTDB

The default database for queries, usually RTDB.

It is not necessary to specify the database name in the Microsoft SQL query if the table is in the default database.

SCHEMA

The schema type (for example NATIVE, ANSI, or ODBC).

Some characters in RealTime column names, specifically dots (.) and square brackets ([ and ]), are not permitted by the SQL-92 naming standards.

When the NATIVE schema is used, column names which contain disallowed characters must be delimited using double quotes. For example "iengr.egumin".NATIVE is the default schema type.

If the ANSI schema is specified, names are expected to substitute @_ for the dots (.), and #_ for both [ and ] in the column names.

If the ODBC schema is specified, substitute : for the dots (.) and {} for the square brackets [] in the column names.

TIMEZONE =

<zone>

Time zone name (for example

Mountain Standard Time).

Changes the time zone of the client so the date/time stamps are calculated according to the client's time zone rather than the server's time zone.

Time zone names may be either Windows-style (for example Mountain Standard Time) or ZoneInfo/ Eggert-style (for example America/ Edmonton).

If you use the Windows-style names, use the "Standard" rather than the "Daylight" name. Daylight savings is still taken into account if the "Standard" name is used.

Note: When the DAL is used to connect to the Microsoft SQL Engine, the client computer's time zone is automatically detected and used in the connection string.