SQL Replication captures changes to source tables and views and uses staging tables to store committed transactional data. The changes are then read from the staging tables and replicated to corresponding target tables.

You can use SQL Replication for a variety of purposes that require replicated data, including capacity relief, feeding data warehouses and data marts, and auditing change history.

You can replicate continuously, at intervals, or for one time only. Replicating continuously can be useful if your applications need data in near-real-time, such as applications for making airline reservations. Replicating at intervals can be useful for replicating large batches of data during off-peak hours. You can also trigger replication through database events.

Sources and targets can be either in DB2® databases or in non-DB2 relational databases. You can replicate from sources and to targets in the following relational database management systems: DB2 on z/OS®, on Linux, UNIX, and Windows, and on IBM® i; Informix®; Microsoft SQL Server; Oracle; Sybase; and Teradata (target only).

You have considerable flexibility with the data that you want to replicate. You can replicate all rows and columns of a table or just a subset. By subsetting rows and columns, you transport across your network only the data that you want.

You can also clean, aggregate, or otherwise manipulate data. If you manipulate data, you can do so centrally at the source and then distribute the manipulated data, or you can manipulate the data when you replicate it, so that some targets get manipulated data and others do not.

With SQL replication you can also automatically generate definitions to integrate staging tables with InfoSphere® DataStage® to provide a continuous flow of data for dynamic warehousing.