Professional Documents
Culture Documents
Staging What is a staging area? Do we need it? What is the purpose of a staging
area?
Staging area is place where you hold temporary tables on data warehouse
server. Staging tables are connected to work area or fact tables. We basically
need staging area to hold the data and perform data cleansing and merging
before loading the data into warehouse.
Data marts How are data marts and data warehouses related? Data Mart is a subset
of data warehouse, a data mart is a repository of data that holds information on
a specific business area. The data warehouse will be made up of a number of
data marts.
Data What is data dictionary?
It is a Metadata repository; it contains information about data such as meaning,
dictionary
relationship to other data, origin, usage and format. It provides information
about the database and has the following features:
• The definitions of all schema objects in the database (tables, views,
indexes, clusters, synonyms, sequences, procedures, functions,
packages, triggers, and so on)
• How much space has been allocated for, and is currently used by, the
schema objects
• Default values for columns
• Integrity constraint information
• The names of Oracle users
• Privileges and roles each user has been granted
• Auditing information, such as who has accessed or updated various
schema objects
• Other general database information
So, it could simply be a MS Word document that describes each table we have,
the columns of various tables, the description of columns (why is that column
there, what is the purpose of it?; sometimes columns are deprecated so this data
dictionary will contain information about it;).
Say there were two columns, one that said TStamp1 and TStamp2. These
column names are not very descriptive or intuitive in what they mean (or what
kind of data they hold). In the data dictionary, the creator of this table can say
“TStamp1 is used to store the last login date for the user. TStamp2 is used to
store the last logout date for the user”.
Meta data is data about the data! So, data dictionary is the way you give the
world information about meta data!
How does one create data dictionary? One can do it manually! But, the
problem with this approach, if the database schema is changing fairly often is
that one can end up spending a lot of time doing this. I have used a tool called
StoneField to create data dictionary (You can elaborate it once you get the basic
dictionary).
ODS contains high granular data with limited history that contains current or
near time data. A typical ODS may contain 30-60 days of information, while a
data warehouse typically contains years of data. ODS act as a staging area for
data warehouses and data marts used for data analysis.
• An ODS is a flat structure. It is just one table that contains all data. Most
of the time you use an ODS for line item data.
• ODS is based on two dimensional model.
• ODS have an option to overwrite or add single record.
Data flow: Operational System ODS data warehouse
For example MS Excel files are a type of database. They are given specific
names, date modified and date last accessed. This is the metadata of the actual
MS Excel database.
Lookup table A lookup table is the table placed on the target table based on the primary key
of the target. It updates the table by allowing only modified records based on
lookup conditions.
Star schema Snow schema is a type of organizing the table so that we can retrieve the result
from the database quickly in a warehouse environment.
Snow flake Snowflake schema, each dimension has a primary dimension table, to which one
schema or more additional dimensions can join. The primary dimension table is the only
table that can join to the fact table.
Star schema Star schema: A single fact table with N number of Dimension, all dimensions will
vs. be linked directly with a fact table. This schema is de-normalized and results in
snow schema simple join and less complex query as well as faster results.
Snow schema: Any dimensions with extended dimensions are know as snowflake
schema, dimensions may be interlinked or may have one to many relationship
with other table. This schema is normalized and results in complex join and very
complex query as well as slower results.