Table of Contents

Search

  1. Preface
  2. Introduction
  3. Defining a System
  4. Flattening IDTs
  5. Link Tables
  6. Loading a System
  7. Persistent-ID (Dynamic Clustering)
  8. Cluster Governance
  9. Static Clustering
  10. Simple Search
  11. Search Performance
  12. Miscellaneous Issues
  13. Limitations
  14. Error Messages

Source Data Types

Source Data Types

The following tables list the supported source data types and what they are converted to for storage in the IDT and IDX.
The first column shows the native data types that can be read from User Source Tables.
The second column shows the equivalent MDM-RE data type documented in the
Files & Views
chapter,
Format & Data Types
section of this manual). Data read from USTs are converted to a common data type to enable combining source data from heterogeneous source database types. For example, an IDT stored on Oracle can be merged from source data read from UDB and MS-SQL Server.
When loading data from flat files instead of USTs, the File and View definitions are specified using these MDM-RE data types. When loading from a UST, files and views representing the UST and IDT are generated automatically.
The third column shows the mapping from MDM-RE data types back to native host DBMS data types. The IDT is stored as a native table on the target DBMS so that it may be queried using SQL. The IDX holds compressed keys and data (MDM-RE data types) and is not user accessible.

Oracle

UST Data Type
Data Type (IDX)
IDT Data Type
F
VARCHAR2
CHAR
VARCHAR2
CLOB
NUMBER (scale > 0)
DATE
2
TIMESTAMP
C
VARCHAR2 /VARCHAR2
CLOB
1
V
VARCHAR2
RAW
BLOB
B
RAW / BLOB
3
I
NUMBER(10) / RAW
4
G
NUMBER / RAW
5
NUMBER (scale = 0)
INT
SMALLINT
N
NUMBER
R
NUMBER
NCHAR
NVARCHAR2
NCLOB
W
NVARCHAR2 /NCLOB
6
X
CHAR
Z
CHAR
1
VARCHAR2 for column lengths <= 4000, otherwise CLOB.
2
DATEs and TIMESTAMPs are converted to C(64) fields by default. The length may be overridden. The default installation date mask determines the date format. This is specified either explicitly with the initialization parameter
NLS_DATE_FORMAT
or implicitly with the initialization parameter
NLS_TERRITORY
. It can also be set for a session with the ALTER SESSION command via a logon trigger defined for the SSA user.
3
RAW for column lengths <= 2000, otherwise BLOB.
4
NUMBER(10) if the length is 2 or 4, otherwise RAW.
5
NUMBER if the length is 2 or 4, otherwise RAW.
6
NVARCHAR2 for column lengths <= 4000, otherwise NCLOB.

UDB

UST Data Type
Data Type (IDX)
IDT Data Type
F
VARCHAR
CHAR
VARCHAR
DATE
8
TIMESTAMP
8
NUMBER (scale > 0)
C
VARCHAR / CLOB
7
V
VARCHAR
B
VARCHAR FOR BIT
DATA / BLOB
9
I
INTEGER
G
INTEGER
NUMBER (scale=0)
DECIMAL
INTEGER
SMALLINT
BIGINT
10
N
NUM
R
NUM
W
VARCHAR / DBCLOB
11
X
CHAR
Z
CHAR
7
VARCHAR for column lengths <= 32000, otherwise CLOB.
8
DATEs and TIMESTAMPs are converted to C(64) fields by default.
9
VARCHAR FOR BIT DATA for column lengths <= 32000, otherwise BLOB.
10
Negative BIGINTs are not supported for use as a PK and/or join column.
11
VARCHAR for column lengths <= 32000, otherwise DBCLOB.

Microsoft SQL Server

UST Data Type
Data Type (IDX)
IDT Data Type
SQL_CHAR
F
VARCHAR / TEXT
12
SQL_VARCHAR
SQL_DATE
SQL_TIME
SQL_TIMESTAMP
SQL_TYPE_DATE
SQL_TYPE_TIME
SQL_TYPE_TIMESTAMP
SQL_NUMERIC
13
SQL_DECIMAL
13
SQL_FLOAT
SQL_REAL
SQL_DOUBLE
SQL_GUID
C
VARCHAR / TEXT
12
SQL_BINARY
SQL_VARBINARY
SQL_BIT
B
VARBINARY / IMAGE
14
SQL_NUMERIC
15
SQL_DECIMAL
15
SQL_INTEGER
SQL_SMALLINT
SQL_TINYINT
SQL_BIGINT
N
DECIMAL
SQL_WCHAR
W
NVARCHAR / NTEXT
16
SQL_WVARCHAR
12
VARCHAR when column length <= 8000, otherwise TEXT.
13
scale > 0 (floating point numbers).
14
VARBINARY when column length <= 8000, otherwise IMAGE.
15
scale = 0 (whole numbers).
16
NVARCHAR when column length <= 4000, otherwise NTEXT.

0 COMMENTS

We’d like to hear from you!