Types of Non DMSII Columns

The DATABridge Client offers several default non DMSII columns (user columns). You can add user columns to the relational database either by using user scripts, as described in this section, or by using the Client Configurator. For more information about the Client Configurator, see the DATABridge Client Console Help.

Note: The Bit column of this table is equivalent to the dms_subtype column of the DATAITEMS client control table, except for bit 14, which is regarded as a dms_subtype of 0.

Bit	Value	User Column Name	Description
1	1	update_type	Database update type, as follows: 0 for extract 1 for create 2 for delete (bit 10 must also be enabled) 3 for modify Note: This value cannot be used at the same time as bit 11.
2	2	update_time	Time the update was applied to the relational database (PC time)
3	4	update_ts	Timestamp of the update to the relational database.
4	8	audit_ts	DMSII audit file timestamp. This column is set to NULL during the initial clone. Note: This bit cannot be used at the same time as bit 13.
5	16	audit_filenum	Audit file number Note: If you use a decimal number, its precision must be at least 4. Otherwise, the value may be too large and result in a SQL error.
6	32	audit_block	Audit block serial number (ABSN)
7	64	source_name	Data source name
8	128	source_id	Data source identifier as defined in the DATASOURCES client control table
9	256	my_id	Identifies the column using the sequence number assigned to the record at record creation time (in the case of SQL Server). Updates have no effect on this number. Important: For Windows Clients only: this column does not appear on non-SQL systems even if requested.
10	512	deleted_record	Delete indicator (key item). A nonzero value indicates that the record is deleted. This is actually the value of the client machine’s clock at the time of the deletion. Making this column part of the index allows multiple instances of a deleted record to coexist without being considered duplicate records. Note: This bit cannot be used at the same time as bit 11. These types are compared in Preserving Deleted Records.
11	1024	update_type	Expanded database update type as follows: 0 for extract 1 for create 2 for delete 3 for modify Note: Be aware of the following: If you reuse the key for this record, it is removed when the duplicate (new) record is inserted. This value cannot be used at the same time as bit 1 or bit 10. Bits 10 and 11 are compared in Preserving Deleted Records. This bit and bit 1 work in the same way, except that this bit preserves the deleted image.
12	2048	source_id	Data source identifier as defined in the DATASOURCES client control table (key item)
13	4096	audit_ts	Expanded audit file time. This column contains the DMSII audit file timestamp during updates and the starting time of the data extraction during extraction. Note: This bit cannot be used at the same time as bit 4.
14	8192	user_column1	Generic user column whose entry is left as NULL
15	16384	sequence_no	A sequence number used in history tables to determine the order of updates when they have the same update_time values
16	32768	delete_seqno	Augments the deleted_record column with a sequence number to provide higher granularity and avoid creating duplicate deleted records.

The bit numbers, decimal values, and hexadecimal values for the user column names are shown in the following table.

Default Name	Bit Number	Decimal Value	Hex Value
update_type	1	1	0x00000001
update_time	2	2	0x00000002
update_ts	3	4	0x00000004
audit_ts	4	8	0x00000008
audit_filenum	5	16	0x00000010
audit_block	6	32	0x00000020
source_name	7	64	0x00000040
source_id	8	128	0x00000080
my_id	9	256	0x00000100
deleted_record	10	512	0x00000200
exp_update_type	11	1024	0x00000400
source_id_key	12	2048	0x00000800
exp_audit_ts	13	4096	0x00001000
user_column1	14	8192	0x00002000
update_seqno	15	16384	0x00004000
delete_seqno	16	32768	0x00008000