Difference between database and data warehouse In this blog we will start with the basics on the data

side and then move on to reporting, modeling, and data-mining. A good Data Warehouse is the first step to wards a sustainable analytics initiative, and unfortunately this is where most p rojects end up going wrong. Some of these posts are lifted from another blog of mine, and they serve to set the perspective and the base that further work would be built upon. So how is a data warehouse different from you regular database? After all, both are databases, and both have some tables containing data. If you look deeper, yo u'd find that both have indexes, keys, views, and the regular jing-bang. So is t hat 'Data warehouse' really different from the tables in you application? And if the two aren't really different, maybe you can just run your queries and report s directly from your application databases! Well, to be fair, that may be just what you are doing right now, running some EO D (end-of-day) reports as complex SQL queries and shipping them off to those who need them. And this scheme might just be serving you fine right now. Nothing wr ong with that if it works for you. But before you start patting yourself on the back for having avoided a data ware house altogether, do spend a moment to understand the differences, and to apprec iate the pros and cons of either approach. The primary difference betwen you application database and a data warehouse is t hat while the former is designed (and optimized) to record , the latter has to b e designed (and optimized) to respond to analysis questions that are critical fo r your business. Application databases are OLTP (On-Line Transaction Processing) systems where ev ery transaction has to be recorded, and super-fast at that. Consider the scenari o where a bank ATM has disbursed cash to a customer but was unable to record thi s event in the bank records. If this started happening frequently, the bank woul dn't stay in business for too long. So the banking system is designed to make su re that every trasaction gets recorded within the time you stand before the ATM machine. This system is write-optimized, and you shouldn't crib if your analysis query (read operation) takes a lot of time on such a system. A Data Warehouse (DW) on the other end, is a database (yes, you are right, it's a database) that is designed for facilitating querying and analysis. Often desig ned as OLAP (On-Line Analytical Processing) systems, these databases contain rea d-only data that can be queried and analysed far more efficiently as compared to your regular OLTP application databases. In this sense an OLAP system is design ed to be read-optimized. Separation from your application database also ensures that your business intell igence solution is scalable (your bank and ATMs don't go down just because the C FO asked for a report), better documented and managed (god help the novice who i s given the application database diagrams and asked to locate the needle of data in the proverbial haystack of table proliferation), and can answer questions fa r more efficietly and frequently. Creation of a DW leads to a direct increase in quality of analyses as the table structures are simpler (you keep only the needed information in simpler tables), standardized (well-documented table structures), and often denormalized (to red uce the linkages between tables and the corresponding complexity of queries). A DW drastically reduces the 'cost-per-analysis' and thus permits more analysis pe r FTE. Having a well-designed DW is the foundation successful BI/Analytics initi atives are built upon.

If you are still running your reports off the main application database, answer this simple question: Would the solution still work next year with 20% more cust omers, 50% more business, 70% more users, and 300% more reports? What about the year after next? If you are sure that your solution will run without any changes , great!! However, if you have already budgeted to buy new state-of-the-art hard ware and 25 new Oracle licenses with those partition-options, and the 33 other c ool-sounding features, good luck to you. (You can probably send me a ticket to H awaii, since it's gonna cost you just a minute fraction of your budget) It's probably simpler and more sensible to create a new DW exclusively for your BI needs. And if you are cash strapped, you could easily do that at extremely lo w costs by using excellent open source databases like MySQL. Comment on above BLOG 1) The real difference between database and warehouse is as simple as looking at the Wal-mart's Merchendise Storing Vs. Distributing to a required locations dep ending on the stores needs. Some stores will not sale certain products, quality and types of merchandize comparing it with the other stores locations. Similarly Database is to received, and entering information that to be stored in a centra lized server and Data Warehousing is to save them, distribute them in the form o f daily updated in order to keep transactions accruate per users need. Not all t he users have a needs for the same data in same format. Warehousing data provide s flexible opportunity for data to be used in multiple places for a specific nee ds. 2) technically db and dw are same, because dw is also based on db. db is the bas ic tool for dw, dw is more of a concept. in the aspect of the content, they are different, because dw has more historical data and oriented for data analysis. d w sometimes contains the concept of dm as well, which is based on dw, and utiliz ing the multidimensional star schema for fastening the analytical procedure FROM ANOTHER BLOG DIFFRENCE BETWEEN DATABASE AND DATA WAREHOUSE 1) Database is the place where the data is taken as a base and managed to get av ialable fast and efficient access. Dataware house is the place where the application data is managed for analysis a nd reporting purposes. 2) Database:It store data in the form of tables,if u want to access data by giveing query, u can retrive data from the database. DataWarehousing:Def:- It is subject oriented,historical,timely variented,integrated and collect ion of data is called datawarehouse. It is one type of techonolgy. In this data call as Dimensions and useful for Anaysis and Reporting purpose. It contains complete data like past and present based on OLTP systems. 3) Normally Database is used for storing the data in the form of tables. And the table will be updated or overwritten depending upon the business requirement. DataWare house DataBase is used for query and analysis i.e the data is never del eted. We can compare the old data as more and more data added . 4) I will explain difference between data base and dataware house in the languag e of layman. Data base is like a market from where you can buy any product but d ata ware house is like a big store like Kmart, SEARS where Every thing which is there is according to the need of surrounding people. Here in this big store al l products are according to the need of customers in arranged manner. All secti ons are clearly indicating the category of items. Its very easy for customers to

grab what they need. same is here in data ware house. We usually bring the requ ired data which is needed for the particular bussiness and it fulfilled the req uirements of business. We use different Bussiniess intellegence tools to extact the data e-g cognos 5) The differences are Database hold current data Stores detailed data Data is dynamic, Repetitive processing, High level of transaction throughput, Predictable patter of usage Application-oriented and Support day-to-day decision While data warehouse holds historical data, Stores detailed, lightly and highly summarized data Data is largely static, Medium to low level of transaction throughput, Unpredictable pattern of usage, Analysis driven, Subject-oriented and support strategic decisions The main advantages of data warehouse are 1- High query performance 2- Queries not visible outside warehouse 3- Local processing at sources unaffected 4- Can operate when source unavailable 5- Can query data not stored in DBMS