SQL Data Types for Tag Parameters

In practice, only a few SQL data types are used. In earlier versions of VTScada / VTS, these determined the type for the matching database column. In modern use, they are used as a hint for how VTScada should interpret the stored information. (For example, whether 0 should be read as an integer or text.)

The full list of available SQL data types follows. Notes are added where needed.

• SQL_LONGUNICODE
• SQL_NVARCHAR
• SQL_BIT
• SQL_TINYINT
• SQL_BIGINT
• SQL_LONGVARBINARY
  Values of any parameters of type SQL_LONGVARBINARY will NOT be converted from the current Windows code page to UTF-8. These parameters are presumed to contain data where the bits are important rather than the characters, and any conversion would alter these.
• SQL_VARBINARY
  Values of any parameters of type SQL_VARBINARY will NOT be converted from the current Windows code page to UTF-8. These parameters are presumed to contain data where the bits are important rather than the characters, and any conversion would alter these.
• SQL_BINARY
  Values of any parameters of type SQL_BINARY will NOT be converted from the current Windows code page to UTF-8. These parameters are presumed to contain data where the bits are important rather than the characters, and any conversion would alter these.
• SQL_LONGVARCHAR
• SQL_PHRASEID
  This marks a parameter as one that stores a PhraseID. This means that if the tag uses the default config folder, then a PPhraseEdit will be used to edit that parameter instead of a PEditField.
• SQL_UNKNOWN_TYPE
• SQL_CHAR
• SQL_NUMERIC
• SQL_DECIMAL
• SQL_INTEGER
• SQL_SMALLINT
• SQL_FLOAT
• SQL_REAL
• SQL_DOUBLE
• SQL_DATE
• SQL_TIME
• SQL_TIMESTAMP
• SQL_VARCHAR