Operational Data Store (ODS)

-
What is an ODS?


An environment:
  1. where data from different OLTP databases is integrated
  2. which provides a view of enterprise data
  3. that addresses operational challenges across more than one business function

Characteristics of ODS:
  1. subject-oriented - catered to specific function or application (customer-centricity, risk management)
  2. integrated - from multiple legacy systems or new and legacy systems
  3. timely - data is continuously/ frequently being updated, typically more frequently than daily
  4. current - data is typically current with little history
  5. detailed - data is sufficiently detailed; not only at a summarized level
  6. central version of reference data
ODS should be a separate data store from the data warehouse.

Difference between ODS and Data Warehouse

ODSDW
Data CurrencyCurrent/ near-currentHistorical snapshot
Data LoadingInsert/ Update/ Deletion allowedOnly loaded

Comments

Post a Comment

Popular posts from this blog

Understanding ITIL Service Management the UML way…

-
Image
I originally had a great deal of difficult reconciling the differences amongst ITIL Change Management, Incident Management, and Problem Management. Having researched on the subjects and understanding them better now, I’ve tried to put the concepts together using a UML class diagram to capture my understanding and to keep it imprinted. Similarly, I wanted to differentiate the various categories of changes (Standard, Emergency, Normal) using an easy to understand & self-explanatory manner – a UML Activity Diagram!
Read more

Apache Web Server Troubleshooting

-
How to troubleshoot Apache Web Server? A few standard commands to know by hard: To confirm the modules that are or will be loaded in Apache: apachectl –M [-f <conf filename>] To check the virtual host load pattern: apachectl –S [-f <conf filename>] To test a httpd.conf file: apachectl –t [-f <conf filename>] To maintain the http server: apachectl start|stop|restart To start with a specified configuration file: apachectl –f <conf filename> Create a minimalist httpd.conf. Something like: Listen 80 ServerName myserver.com:80 ServerAdmin admin@myserver.com #ServerRoot " . " ServerRoot " /usr/local/apache2 " User nobody Group nobody #DocumentRoot " ..\wwwroot " DocumentRoot " /home/data/html " ErrorLog " logs/basic_apache.log " LogLevel debug #LoadModule log_config_module modules/mod_log_config.dll LoadModule log_config_module modules/mod_log_config.so <IfModule log_config_module> LogFormat " %h %l
Read more