July 20, 2009 at 12:41 am
Hi experts
Hi i would like to know the realtime replication issues in production servers.
generally what kind of issues and solutions will face in the live environment
in future we will be going to use this replication and ligshipping .
reply
regards
July 20, 2009 at 1:07 am
your biggest problems normally come from connection problems if one of the servers is offsite etc. Data issues (checking the validity of data at both sides). if your using merge repl then how do you handle conflicts.
Log shipping - what do you do when somebody breaks the log chain. if the primary server goes down do you know how to bring the secondary server up. if the log fails to restore on the secondary server what should you do.
there are many different types of errors in any replication configuration so its hard to answer such a general question.
July 20, 2009 at 2:23 am
Is this out of interest or do you have a real-life problem with an environment? If so have you considered mirroring?
Replication is generally problematic to set up and get working (setting not for replication and ensuring triggers dont fire went not wanted etc). Once you do get it working it is not bad; however if it ever breaks (or you have a comms black-out you generally have to scrap and re-sync (very time consuming)).
Unlike Log Shipping, mirroring has a much smaller latency (not scheduled) and breaks in comms arent that problemantic (when running without Witness server). Like log shipping the mirror db will be offline and not accessible for reporting purposes (like with replication) but i have found Mirroring to be more reliable then each of the other options.
Adam Zacks-------------------------------------------Be Nice, Or Leave
July 20, 2009 at 5:39 am
Hi,
It may help if you are able to tell us a little bit more about your environment and/or application because as with most SQL Server technologies, their suitability is dependent on the problem that you are looking to specifically address.
For example, as other posters have mentioned, the maintenance overhead with Replication can be quite involved if you need to create a complex deployment.
Whereas if your deployment is straightforward, for example you wish to offload Reporting to another server, then typically you need only to copy a subset of the production database data. Such a configuration would require limited management.
Start by telling us a little bit more about the requirements of your project/application thereby allowing us to provide more specific guidance.
Cheers,
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply