Uncategorized

David Loshin 0
Integration planning for master data management

A few years ago, I was presenting a morning course on master data management in which I shared some thoughts about some of the barriers to success in transitioning the use of a developed master data management index and repository into production systems. During the coffee break, an attendee mentioned

Joyce Norris-Montanari 1
Estimating time for data modeling

THIS IS HARD TO DO! In our agile world we seem to never get the data model completed until two weeks after we are in production, and every project plan wants to waterfall the completion of this deliverable. I think it may be due to the rapid way we gather and refine requirements. For

Dylan Jones 0
Make data quality dimensions work for you

One of the most common questions I get asked by our members on Data Quality Pro is, “Can you do more articles on data quality dimensions?” Part of the reason for this request is when people first start getting involved with data quality, they invariably buy data quality books and

Jim Harris 0
The psych to silo and the right to copy

In my three previous posts, I pondered whether unlimited data could limit data silos (i.e., whether offering users the enterprise data management equivalent of unlimited data streaming could curb their enthusiasm for creating data silos), or if streaming past the limits of unlimited data could create more data silos if users became frustrated with the practical

Tamara Dull 2
We need Hadoop to keep our data costs down

You’ve read the research reports and seen the statistics. You’ve attended the conferences and heard the case studies. You’ve read the online articles and kept up with expert opinions. Your organization has even done a few big data sandbox projects – some successful, some not. Yet the jury is still

David Loshin 0
Entity resolution in isolation

The conclusion from my last post was that entity resolution can indeed exist as a product that can remain segregated from master data management (MDM). However, the benefit of integration with MDM is that its utilization is directly embedded within the MDM application, which reduces the level of expertise the

Joyce Norris-Montanari 3
Business terminology vs. technical lingo

How many meetings have you been in where the technical personnel start talking about the database, sizing, storage, partitioning, indexes, staging, ETL, programs, operations or performance – and the business users in the group look perplexed? When you're meeting or gathering requirements with business users, "techno lingo" can sure make

Dylan Jones 0
Thoughts on data quality diminishing returns

Jim Harris recently penned an interesting article describing what happens to data quality at the top of the bell curve. The central theme of the article explains how, as we strive for greater levels of quality, we hit diminishing returns. For example, the cost of sending an engineer down a

Jim Harris 0
Syncing versus streaming

In my two previous posts, I pondered whether unlimited data could limit data silos (i.e., whether offering users the enterprise data management equivalent of unlimited data streaming could curb their enthusiasm for creating data silos) or if streaming past the limits of unlimited data could create more data silos if users

David Loshin 0
Entity resolution outside of MDM

In my last post, we explored the integration of entity resolution technology as a core component of a master data management (MDM) application, and I raised the question as to whether the rampant phase of acquisition and integration of entity resolution tools companies into MDM solutions providers implied that the

1 65 66 67 68 69 105