Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

What is the format of a data dictionary?

Tags:

database

Are there any standard examples/ samples of data dictionaries that document a database.

like image 493
Srikar Doddi Avatar asked Jun 22 '10 17:06

Srikar Doddi


People also ask

What should be in a data dictionary?

Data dictionary contents can vary but typically include some or all of the following: A listing of data objects (names and definitions) Detailed properties of data elements (data type, size, nullability, optionality, indexes) Entity-relationship (ER) and other system-level diagrams.

What is a data dictionary example?

For example, a bank or group of banks could model the data objects involved in consumer banking. They could then provide a data dictionary for a bank's programmers. The data dictionary would describe each of the data items in its data model for consumer banking, such as "Account holder" and "Available credit."

What are the five components of data dictionary?

Within the data dictionary, there is a singular source of reference for various data attributes, such as: business definitions, constraints, data type, default values, length and transformation regulations.


1 Answers

The official standard is ISO/IEC 11179 ... which will make your head hurt and refers to semantic elements of the documented data-model when we usually need both semantic and physical (tables, fields etc.) documentation in a 'real world' data dictionary.

Personally, I favour (however you implement this is up to you) physical and optionally logical Entity-Relationship models on the front-page, entry screen or wherever a user of the Data Dictionary first 'hits' (This provides a meta layer to the detail beneath).

Then for each table:

Table Name [Physical | Logical]

Table description (content, granularity, 'periodicity' (if there is one, the time period which applies to the data contained in the table), source)

Then for each column:

Column Name

Column Description

Column Datatype

Column Size in Bytes

[Optional] Other Column Details... nullable, triggers, source

Relationships Constraint name | 'Other' Table | Cardinality | Type etc.

Indexes Name | Column Membership | Type etc.

...Obviously, that's a 'less is more' approach to defining a data dictionary! I think the key is providing an easy way in (through the ER) model, rather than just a long, labourious list of tables and columns.

like image 124
bochgoch Avatar answered Oct 02 '22 16:10

bochgoch