SQL Server Database Creation Requirements |
Virtual Machine |
 |
The uniqueness of data can depend on character set and sort order applied to the database at the time of database installation. Once set up, this cannot be easily changed. The default sort (collation) order for databases may not be compatible with the standard order used by PROISAM; sorted records may display in a different order than expected. This difference can be a source of programming/data migration headaches if the PROIV database system is changed. Ensure that you understand the ramifications of the RDBMS installation options before creating databases.
A PROISAM-compatible collation sequence for SQL Server is BIN_850 with a CodeSet of 1250. A similar setting for DB2 is 'Identity'.
The following restrictions apply:
-
The database name, user name and password to connect to the relevant SQL RDBMS must be specified externally to PROIV.
-
There is a 254 column restriction on the SQL file definition.
-
The pseudo-keys in a PROIV file definition for an SQL table must uniquely identify individual rows. PROIV cannot handle duplicate keys for SQL file types on primary keys.
-
The browse facility has indeterminate results in non-paging screens and is therefore not supported.
-
Group-occurs, redefinition and encryption are not supported in file definition.
-
Company/division dependent files are not supported.
Topic ID: 560056