Data warehouse

• Code (field COD)

This code identifies the current record in a unique way.

• Description (field INTIT)

Use this field to assign a description to each record.

• BI solution (field SOLBI)

Defines the code of the solution where the BI data will be installed.

• Machine (field MACHINE)

Network path defining the remote server to be connected to.

• Type of OS (field TYPOS)

Defines the operating system on which the data structure of the business intelligence runs.

• Database type (field TYPDBA)

Define the database used to create the folder. This database can be SQL SERVER or ORACLE. As a function of the license that is used, this choice may be possible or imposed.

• Name of the database (field DATNAM)

• Directory (field REP)

Installation disk address for the remote solution. It is this location that the directory that is used in the remote connection will be created if a folder of the same code as the current folder does not exist.

This address corresponds to a database directory (volume 0 in adxvolumes) on the application server.

• Data size (field SIZDAT)

These values are used to size the data files and the index in the database. The size is expressed in Mega-bytes.

These values are only interesting from the point of view of folder creation, and they are generally entered at the end of the definition of the folder parameters, just before the actual folder creation. In fact, to have available a correct estimate for the value, it is important to have previously sized the database tables by means of the sizing values ( Tables tab), and to have more importantly defined the table structure of the database by means of the activity codes (Options, Screens, Specifics).

• Index size (field SIZIDX)

• Format (field CODDBA)

Defines the set of characters used to store the character fields in the database. It can take the values ASCIIor UNICODE.

• The ASCII format is used for managing European languages: each character is stored on one byte and the accented characters on values higher than 128.

• The UNICODE format is only useful when managing languages having sets of characters requiring over 256 combinations. This is the case for Chinese, for example.
  The SAFE X3 client is native UNICODE: it inherently ‘knows’ how to manage texts of this type. It can elect to choose one of the two following formats at the level of the database: UCS2 or UTF8.
  
  The UCS2 format is a format originating with Microsoft™ in which all characters are stocked in 2 bytes; the normal ASCII characters have the same code (but one of the two bytes in which they are coded is null). This is the only UNICODE format type that is supported by SQLServer. On the other hand Oracle accepts other formats, and in particular the UTF8 format, which is the most common. It features a format in which the characters are stored over a variable number of bytes (from 1 to 5 depending on the cases, the standard ASCII characters are stored over one byte, the accented characters use two and the Asian languages start beyond). It should be noted that Oracle supports other coding standards (UCS3, UCS4, UTF16...) and these standards can be used (on the condition that they are created manually in the database).

Internally and independently of the database format (for its temporary variables), the SAFE X3 engine uses the UTF8 format (the process sources are coded in UTF8), and the Windows client uses the UCS2 standard.

• Use file groups (field GRPFIL)

This question is asked in the case of a SQL database server is used to define if separate files are created or not to store the indexes and the data (for the important databases this is the normal case).

• Datasource (field DATSRC)

• Language (field LAN)

Code controlled in the language table and used to define the language of creation of the universes associated with the datamart.

• Datamart (field CODABM)

Defines the datamarts to be created in the datawarehouse.

• Folder (field ADXDOS)

Defines the X3 folder from which the datamart is populated.