Synchronizing Data Among Heterogeneous Databases

INTRODUCTION TO HETEROGENEOUS REPLICATION
Not so long ago, a company’s data was all stored in a central data repository. Users who needed access would have to create a remote connection or in many cases, required an actual printout of the data. This wasn’t too much of a problem when a company acted locally, or had a centralized main office with mainframe computers that controlled the company’s data. From this centralized data storage paradigm, the industry has moved to a much more distributed architecture with Client/Server applications becoming the norm. Mergers, acquisitions, and globalization have also necessitated a more distributed data storage model. As companies are acquired or global offices are opened, data needs are often determined at a departmental level. Globalization has resulted in the distribution of data across many different systems, applications, and vendors. This has led to a great many problems, with inconsistent, out-of-date, or duplicate data that can’t be trusted or relied upon. Acquired companies or remote offices often make their own decisions about, or bring with them, databases from many different vendors. This further complicates the process of maintaining current, relevant, and correct data at each location.

How can a company make sense of this situation, keeping their data current, relevant, and correct across many different heterogeneous applications and databases? The databases at remote sites must be kept current with changes between sites or between main and standby databases. Sybase Replication Server® has all of the features you need to keep your databases in synch.

This paper will describe Sybase Replication Server and how it enables the user to keep heterogeneous databases synchronized.

Click here to view the complete document (PDF).