Hello DBA world :)
Kindly, i am working on configuring a MS SQL Replication on SQL Server 2008R2 to replicate data from Source DB( SQL Server 2008R2) on Server 1 to Destination DB (Oracle 11g) on Server 2
I had configured the replication successfully after installing the 11g oracle client driver and any changes occurs on SQL DB (Source) replicated in less than a sec. to Oracle 11g DB (Destination)
The point is that the Replication during initialization creates a snapshot of source SQL DB data and re create the destination Schema. which means no historical data will be in destination database, and no schema difference between source and destination Databases.
And any schema difference can be happened after the replication has been already initiated.
Our requirements which need to be maintain are:
1- Configure the MS SQL Server Replication without deleting or changing any historical data exists in the destination Oracle DB which exists before replication configuration during the replication initiation (Overriding replication initiation snapshot) and
historical data can be changed if changes happened on source database after replication starts on the same historical data on source DB.
2- Start Replication without changing Destination Oracle Schema, and keep destination schema with out changing during replication initiation (Overriding replication initiation snapshot)
Taking into consideration, that i had tried to edit the ( .SCH , .PRE) files to prevent creation of schema during the replication initiation. however if the schema not identical in source and destination DBs the replication initiation fails through error, (Can
not apply Bulk insert during initiation due to schema difference) and we need to keep the destination schema difference as it is.
Is there any Solution or configuration to fulfill the above 2 requirements during replication initiation and override its own basic rules?
3 further question if anyone can help:
1- if there was a data constrains somehow on a certain column in the destination database which not allow certain data value to be inserted in one of the tables, and the source database contains such a data which will be transfered by the replication to destination
db, and the constrain prevent the data to be inserted, so the whole replication will fail or that certain record only will fail?
2- What is the best practice monitoring tool or way to monitor the replication?
3- Can i script the whole replication solution with any further customization did on the replication configuration and deploy it on different servers automatically?
Wish if anyone can help please.
Best Regards
Shehab Saad