Designing an ODS with high availability and consistency

Designing an ODS with high availability and consistency Name Arshad Ali Title SDE 2 Company Microsoft India

Approach 1 Traditional Model Sales Marketing Finance HR Other Sources ETL Processes ODS space Operational Data Store Database Data Access Point (DAP) Client A Client B Client C

Approach 2 Database Snapshot Model Sales Marketing Finance HR Other Sources ETL Processes ODS space Operational Data Store Database Snapshot Data Access Point (DAP) Client A Client B Client C

Approach 3 Data Publication Model Front Server 1 Marketing 1. ETL Server ETL Processes Finance ODS Database 2. Data Publish Clone 1 A Front Server 2 HR Other Sources Clone 2 A 3. Data Access Point (DAP) Sales Client A Client B

Approach 3 Data Publication Model Front Server 1 Marketing 1. ETL Server ETL Processes Finance ODS Database 2. Data Publish Clone 1 A Front Server 2 HR Other Sources Clone 2 A 3. Data Access Point (DAP) Sales Client A Client B

Approach 3 Data Publication Model Sales ETL Server Marketing Finance HR Other Sources 2. 1. ODS Database ETL Processes Clone 1 A Front Server 2 Clone 2 A Data Publish Clone 1 B Clone 2 B Data Access Point (DAP) Front Server 1 Client A Client B

Approach 3 Data Publication Model Sales ETL Server Marketing Finance HR Other Sources 1. 2. Clone 1 A Front Server 2 Clone 2 A ODS Database ETL Processes Data Publish Clone 1 B Clone 2 B Data Access Point (DAP) Front Server 1 Client A Client B

Approach 4 ODS on Cloud – A look into future Sources outside cloud Sources on cloud ETL Processes ODS Database (Microsoft SQL Azure) ODS space Database Snapshot (Microsoft SQL Azure) Data Access Points (DAP) Client A Client B Client C

© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U. S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.