Archive for 'Data Integration'
Apr 30, 2013 by David Loshin
Last time we looked at how the tools and methods incorporated within a master data management system can contribute to ensuring the satisfaction of the success criteria for data warehouse consolidation. MDM provides some valuable capabilities that will simplify the consolidation processes.
Apr 23, 2013 by David Loshin
In the past few postings we looked at some of the issues that emerge as a result of uncontrolled creation of data warehouses and data marts. I suggested that the goals of a data warehouse consolidation project should not only include the creation of a new data asset that accommodates the users of the “to-be-consolidated” warehouses and marts, but that those systems should be retired and replaced by the new asset.
Apr 16, 2013 by David Loshin
The last thing you want to result from a data warehouse consolidation project is the creation of yet another siloed data asset that must be populated and managed with respect to the requirements of the downstream users.
To really benefit from a consolidation project, your newly-created consolidated warehouse should replace the data marts and warehouses that are used to populate…
Mar 11, 2013 by Joyce Norris-Montanari
To allow file uploads into your business intelligence environment or not to allow file uploads – what is your decision? I have a tendency to look at this issue like this:Someone on the business side needs this data – and probably needs to looking at existing data another way. For example, rolling up sales data to different sales regions or categories. The…
Mar 05, 2013 by David Loshin
Last time we began to look at the opportunity for integrating a newly developed master data repository with existing business applications supported by a data warehouse. That meant understanding the requirements for integration and verifying that those requirements are met.
Feb 19, 2013 by David Loshin
By evaluating data dependence relationships as part of the process of integrating a data warehouse with a master data repository, one begins to see patterns of at least three key types of accesses. A search or locate access queries the master repository to determine if an entity already exists within the master data set, a read accesses the data, and an update will modify the data in the master repository.
Feb 12, 2013 by David Loshin
Master data not only serves as an index and registry for entities that are managed within data warehouses, they can also be used as tools to drive and support the consolidation of multiple data warehouses into a single, unified data warehouse.
Jan 08, 2013 by David Loshin
How do you balance the costs and benefits of copying data? Seems like a simple (or perhaps simplistic) question, but the answer actually can provide the perspective for performance measures that influence a system design. For example, an objective for creating a data mart to support many individual queries each day as part of a workflow process requiring up-to-date data is very different from creating a data mart for generating the reports for the previous day’s transactions.
Jan 02, 2013 by Jim Harris
Welcome to the unofficial 2012 quarterly review that I have decided to perform on the Data Roundtable. In this four-part series, I will select and summarize my favorite posts published on this blog during each quarter of this year, selecting one post per contributor per month.
Part 1 of this series covered blog…