Building Making It Happen
Building Making It Happen
  Sign-in         Register
    
Principles and Rules Listing Page
Using Synonyms and Views
Synonyms and Views create a user friendly layer for user access and querying. They also enable to make underlying database changes with minimum impact on user access interface.
 
This page of 'Principles and Rules' is linked to:  Data Warehousing, Data Analysis/OLAP,


Using Synonyms and Views to better handle the database level changes

This tip is equally applicable for OLTP scenario.

Synonyms or Alias

Synonym is like an alias for a table name at a physical level. The idea is that the query which an end-user tool fires to access the data, should be ideally using a synonym than the actual table name. A synonym (or alias) is just like the name of the book-mark in your internet browser, while the underlying link is pointing to the actual URL. You can maintain the same name of the book mark, while changing the underlying hyperlink.

Similarly, if you use synonym for providing access to the users and end-user tools, the advantage is that you can rename the underlying tables (as your dimensional model evolves), while still maintaining the same aliases or synonym. You can create synonyms for tables, views, stored procedure, function and some other objects. The idea is to have user-friendly synonyms and also to have a better change management.

Views

A view is a virtual table created on which the end-user tools or users can run queries. The views are created to make it easy and user-friendly access to the database. Views are typically created to provide a single table made out of multi-table, complex queries. For example, you may have a snow-flake schema, which you may convert into a star-schema by combining the dimensional table and its extension.  OR you may like to create a single virtual table combining the fact table and dimensional table.

   Access more details on this page   

Quick Feedback- Was this information helpful ?
Relevant Links to this page
Principles & Rules → Dimensional model has to be aligned to the Entity-Relationship → Principles & Rules → Always Use Conformed Dimensions → Principles & Rules → You may not be a able to have a perfect ETL → Practice Techniques → Handling Sparse Dimensional tables → Principles & Rules → Do not separate the parent and child line item data → Practice Techniques → Managing time-stamps across multiple time-zones → Practice Techniques → Recording events in multiple currencies → Practice Techniques → Handle different units of measure in the same fact table → Principles & Rules → Handling of Null foreign Keys in fact tables → Principles & Rules → Dimension Attributes as NULL → Principles & Rules → Don't rely too much on Meta Data Tools to enforce Business Intelligence → Principles & Rules → Don't wait for universal models for Data Marting → 
 
Back
Featured Pages
What is MDM-CDI?
Data Source Checklist
Master-Data-Management CDI Architecture
Data Quality Phase Completion

Make 'Executable' Strategy
Maximize Results
Maximize People
Manage Execution

Featured Pages
One tier Data Warehouse
Always Use Conformed Dimensions
Customer Segmentation Analytics and BI
Data Warehouse Components and Framework