August 5, 2001 at 7:28 am
We want to replicate between to Databases using internet (Web Server at one end and Pc at other end).
Can anyone suggest settings required for replication.
I also want to know whether it is possible to set "flag" to all columns in order to know whether the information / data is replicated or not. This flag will be used to set conditions like "Not to allow the user to make changes after replication"
In absence of this I will like to know how to know which data has been replicated....so that the rule "once replicated cannot be changed" can be set in the system developed using ASP.
August 5, 2001 at 2:42 pm
You're probably want to use transactional replication - but you need to take a look at your goals to make sure. Generally snapshot is too expensive in bandwidth and merge is more complicated than necessary.
As soon as the change is applied you should consider it replicated. Keep in mind also that you may have to "re-replicate" at some point - send over a new snapshot if your subscriber gets out of sync. If you just want to do custom record locking, put a trigger on the table that sets a flag if modified. You could then filter the data so that the users cannot see rows with the flag set.
Andy
December 8, 2002 at 5:19 pm
If you want to keep track of what's been replicated, set up another data base on your same server as a replication subscriber. When replication completes, you will have data in your "shadow" data base that shows the data has been replicated. In your applicaiton, you can test for its presence there and disallow modification in your "real" data base. You can assume it made its way to your other data bases as well.
December 8, 2002 at 6:53 pm
Do however keep in mind that size and overhead for checking the data with that solution.
It would be better if you just disallow edits after initial edit any. Inserts only, no updates, then you do not have to worry. However, no matter what you do there always ways to circumvent so you have to make sure your security model will prevent.
Why do you need to prevent further changes only after replication and specifically why are you replicating. Sounds to me like you should are ultimately going to make changes at the web server and what are you going to do locally to keep the data synced. Which replication will you use. Step back and think about what you want to do and why the n explore all the options and make sure your thoughts are logical in progress.
Always ask WHY?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply