| DataGate® 16.0 for SQL Server Reference Guide
|
Object Considerations
The following table details important object considerations when converting or communicating between DataGate® for IBM i, DataGate® for SQL Server, and the core DataGate® program.
Considerations
|
Item |
DG/400 |
DSS |
DataGate |
|
Library & file name length |
10 characters |
31 characters |
31 characters |
|
File types |
Physical -- Simple logical Join logical Multiformat logical |
Physical SqlLogical Simple logical Join logical -- |
Physical -- Simple logical Join logical Multiformat logical |
|
Max record length |
32,000 bytes |
8,060 bytes (Not counting Text and Image fields that are not accessible yet by DSS). |
32,000 bytes |
|
Max number of records per member |
|
Limit defined by SQL Server instance |
2,147,483,646* |
|
Library implemented as: |
Library |
Database |
Internal construct |
|
Object text (description) |
49 characters |
49 characters |
49 characters |
|
Stored Procedures |
Any AS/400 language |
Programmed in SQL-Transact |
None |
|
Triggers |
Any AS/400 language |
Programmed in SQL-Transact |
None |
|
Field Reference File (FRF) |
A physical file can refer to any number of FRF, which are any physical file in any library. However, DG/400 will report only those coming from the file stated in the DDS REF keyword. |
Refers to the collection of 'User Defined Data Types', which is one per Database (i.e.: Library). This collection is surfaced via the special file '*FieldRef' which is the ONLY file usable as a FRF. |
A physical file can refer to only ONE FRF, which FRF, which can be any physical file in any library |
Note: For Max number of records per member, DataGate® for Windows and Desktop Servers support member/file sizes limit of 16 exabytes ( 2^4 * 2^60).