JUN 23, 2010 5:13pm ET

Related Links

Birst Automates Connections to Big Data
February 8, 2012
The Data Behind Red Cross Donations
February 6, 2012
UBS Taps Big Data to Shrink Reputational Risk
February 6, 2012

Web Seminars

Deliver Better Enterprise Data through Better Reference Data Management
Available On Demand
The Strategic Move - Migrating to a New Data Warehouse Platform
Available On Demand
The Data Dilemma: Is the Answer in the Cloud?
Available On Demand

Updated: TDWI: How To Make Data Integration Work

Print
Reprints
Email

June 24, 2010 – A recent report from TDWI offers a checklist of 10 best practices that shows it’s time to raise the bar on integration expectations as the industry’s evolution has outpaced mindsets.

Philip Russom, senior manager for TDWI Research and author of the report, emphasizes that there's no silver bullet for "ideal" data integration. As the report explains, DI is a diverse discipline that makes use of a number of tools depending on one's business and technological requirements.

DI has undergone an expansion over the last decade and has reached a critical mass of multiple techniques used in diverse applications and business contexts. Vendor products have achieved maturity; users have grown their DI teams to epic proportions; competency centers regularly staff DI work; and DI as a discipline has earned its autonomy from related practices like data warehousing and database administration. Given all this change, it’s not surprising that many DI specialists and the colleagues who depend on them suffer misconceptions and out-of-date mindsets that need adjustment.

TDWI’s report explains a few things to understand about  DI:

  1. Data integration is a family of diverse but related techniques.
  2. Data integration practices reach across both analytics and operations.
  3. Data integration is an autonomous data management discipline.
  4. Data integration is the repurposing of data via transformation.
  5. Data integration is a value-adding process.
  6. Data integration is a green technology that makes data management more sustainable.
  7. A data integration solution should have architecture.
  8. A data integration solution should be the product of collaboration.
  9. Data integration must be coordinated with other data management disciplines.
  10. Data integration should be governed, but also contribute to governance.

"This report is an eye-opener, regardless of who the reader is," says Russom. "Many technical and business people are aware of data integration, but they’re not fully aware of all its capabilities and benefits." Russom explains that even DI specialists sometimes focus on specific tasks  for a deliverable and sometimes grope for meaningful ways to describe the goals of DI. "To help people voice these issues, the report reflects on DI’s true mission and altruistic goals. Hence, for any reader with an open mind, this report redefines data integration and its potential in modern, future-facing terms."

For more detail on these best practices, the report, Top Ten Best Practices for Data Integration, is available for free download.

Valerie Valentine is senior editor for Information Management. You can follow her on Twitter @ValValentineIM.

Advertisement

Comments (0)

Be the first to comment on this post using the section below.

Add Your Comments:
You must be registered to post a comment.
Not Registered?
You must be registered to post a comment. Click here to register.
Already registered? Log in here
Please note you must now log in with your email address and password.
Twitter
Facebook
LinkedIn
Login  |  My Account  |  White Papers  |  Web Seminars  |  Events |  Newsletters |  eBooks
FOLLOW US
Please note you must now log in with your email address and password.