Why Adventureworks sample databases separated OLTP and DW?

Answered Why Adventureworks sample databases separated OLTP and DW?

  • Monday, July 30, 2012 7:16 AM
     
     

    Could you explain me why Adventureworks sample databases separated OLTP and DW?

    If OLTP and DW entities combined one database, It seemed there have no problem, isn't it?

All Replies

  • Monday, July 30, 2012 7:24 AM
     
     Answered
    Because that's the common model: An OLTP for data operation and a DataWarehouse for reporting and/or as base for a OLAP cube.

    Olaf Helper
    * cogito ergo sum * errare humanum est * quote erat demonstrandum *
    Wenn ich denke, ist das ein Fehler und das beweise ich täglich
    Blog Xing

    • Marked As Answer by David Hur Monday, July 30, 2012 9:14 AM
    •  
  • Monday, July 30, 2012 7:44 AM
     
     Answered

    Hi,

    It is because of the differences between architecture of OLTP and OLAP.

    AdventureWorksDW provides a very good practical samples of OLAP.

    OLAP systems generally have very better performance for Analysis and Reporting tasks.

    OLTP systems have good performance for storing data.

    AdventureWorksDW is generated based on AdventureWorks DB just for OLAP purposes.

    Cheers,

    Soheil


    MCP, MCTS, MCITP

    • Marked As Answer by David Hur Monday, July 30, 2012 9:13 AM
    •