Building Making It Happen
Establishing Making-it-Happen as ‘Formal & Measurable’ Business Discipline
  Sign-in         Register
    
   Data Warehouse Test Data  

Execution-MiH Encyclopedia  →   Enterprise Intelligence  →  SECTION -  Data-Warehouse/Mart  →  CHAPTER -  DW Testing and Implementation  → 

Data Warehouse Implementation Deployment

Data Warehouse implementation will need installation of checking in the final version, productionizing, installing client applications, establishing service and support mechanism, user communications and week-end conversion of database.

After the testing phase is complete, the systems are now ready for implementation

List of Tasks for Data Warehouse Implementation and Deployment

Version the DW implementation scripts and environments & Freeze

  • All scripts related to Extraction, Transformation and Loading
  • All configurations of staging and Loading, and access environments
  • All Data in the source systems.

Run the DW productionization processing

  • Run the historical snap-shots (Some times they are done before hand to save time on the implementation weekend).
  • Run the ETL scripts
  • Run the refresh scripts for downstream data marts, systems.

Data Quality and DW implementation Verification

Business analysis teams mainly do this before they hand it over to users for their verification:

Data Warehouse End User Applications

End user applications need not be implemented along with the Data Warehouse. Typically Data Warehouse is implemented along with an OLAP tool and some end-user tools.

Same rigor is followed for end user applications as that of Data Warehouse, in terms of versioning, production processing and verification. Clients of the end user applications are installed and tested.

End User Training

  • The end user training material is ready.
  • A group of power users has already been taken through it (they themselves might be involved in creation of the training material). These power users will act as the trainers for their respective functions.
  • The training material is divided into different category of users- Power users/Designers, Ad-hoc users (typically they place the ad-hoc queries and use the reports generated by the designers) and recipient users. (The users who only view the reports created by designers)

End User Support mechanisms and communication

  • 'Support mechanism for users' is established and communicated (Help line numbers, with in department mentors/trainers, escalation matrix)
  • Support mechanism for technology staff (vendor help lines and escalation matrix.)
  • The reporting and communication framework on defects, and user feedback is established.
 

   Data Warehouse Test Data  
 
All Topics in: "DW Testing and Implementation" Chapter
 Data Warehouse Testing is Different →  Data Warehouse Testing Categories →  Data Warehouse Test Scenarios →  Data Warehouse Test Data →  Data Warehouse Implementation Deployment → 
 
Relevant Links to this page
Practice Tools → Data-Warehouse Deployment Readiness Checklist → 

Was this page helpful?
If you like it ? share it !
Digg
Digg
Reddit
Reddit
Del.icio.us
Delicious
Google
Google
Live
Live
Facebook
Facebook
Slashdot
Slashdot
Netscape
Netscape
Technorati
Technorati
Stumbleupon
Stumbleupon
Spurl
Spurl
Furl
Furl
Blogmarks
Blogmarks
Yahoo
Yahoo
Plugim
Plugim
Squidoo
Squidoo
BlinkBits
BlinkBits
 
CONTENT ZONE
Data-Warehouse/Mart

Featured Pages
Data Quality Assurance and Control Guidelines
Data Warehouse Purpose and Objective
Master-Data-Management CDI Hub Architecture
Data Quality Phase Completion

Make 'Executable' Strategy
Maximize Results
Maximize People
Manage Execution

Featured Pages
OLAP Architecture choice
Beware of Data Federation
Give & Take for Source systems
Excel vs. BI