During the planning phase of a replication project, you should gather all the business requirements that Syniti Replicate will need to fulfill, and precisely determine how the target tables will be derived from the source tables.
The Syniti Administrator and the Database Administrator (whether it is one person who does both or two different persons) will need to ask the following questions before developing a plan for the replication process:
Business Requirements Questions
Is Syniti Replicatebeing used for system backup? Data sharing? Data propagation?
Will the users need current data, or will they be able to work with data that is not current up to the second?
What is an acceptable level of latency for the replicated data? (1 hour, 1 day, 1 week?)
How often do replications need to be scheduled for?
Which data should be blocked (from users, groups of users)?
Will the users need to be able to update the replicated data, or will they only need to read the data?
Will all the users and user groups need the same data, or will they need different subsets of the data?
How will the users access the data? (OS, Hardware, Network)
Are there periods when insert/delete/update activity on source tables is more frequent?
Configuration Questions
How many tables will need to be replicated? How many databases? Use the Database Replication Scenarios and Table Replication Scenarios to help you determine your needs.
What types of replication are needed? (Refresh, Mirroring, Synchronization)
If the users must be able to update the replicated data, is it a problem if someone else updates another copy of the data (same row), elsewhere, at the same time? If it is a problem, how can you prevent such a conflict from occurring, or deal with update conflicts if you cannot prevent them?
If users need different subsets of rows, do you have a sub setting criteria present in all the tables? Is this criteria contained in a column that can be updated in place by an existing application? Will some users need different subsets of columns?
How much data has to be replicated? What is the level of volatility (number of updates/inserts/deletes per hour or per day)?
Are the existing tables normalized, and do you always follow the relational model recommendations?
Will the headquarters of your organization need consolidated data from geographically dispersed data?
Are there special filtering needs?
Related Topics