×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From: Norm Dennis
I'm not disagreeing Buck, just pointing out the obvious.
Data Warehousing was implemented to retain duplicate (redundant) data.
No, duplicate data may be a byproduct of a data warehouse, but not much of a reason for it, if at all. The primary reason for data warehouses is to support business analytics, and sometimes to house an aggregate of data from otherwise disparate sources (multiple business entities) or disparate platforms.
Buck made some extremely relevant points about the huge cost of managing duplicate data across disparate platforms. He deserves more credit. If the primary need is business analytics, then as others have said, you can write queries against an IBM i database as easily as writing queries against disparate databases.
Data replication has a place for business continuity purposes, however. Mirror data to a remote site in order to recover from disasters. Some IBM i organizations kill two birds with one stone. They mirror a production server to an offsite location, and perform business analytics and daily backups off the remote server.
Referential integrity constraints are not needed on a replicated server. I'd suggest using SQL Views to simplify and streamline interfaces between related tables.
-Nathan
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
