Friday, March 9, 2012

Replication of Great Plains Data

Hi All,

We have the requirement to replicate financial data to Aus from the UK, however I dont know if Replication is the best solution around?

Reason why I ask this, is that to create the publication, there are in excess of 10000 articles, which takes forever and a day to create, then when setting up the push subscription, this takes equally as long.

DB's physically range between 100MB and 2GB. Link to Aus is 2MB E1.

The accounts server isnt the most powerful of beasts (HP DL380, 1x1.4Ghx CPU) and with 4 DB's to setup and replicate, it's going to take some time.

With this in mind, I would also be looking to script out the publication should there be any failures and put it into SourceSafe, however this would also take a vast amount of time.

I've thought about using Log Shipping, however I dont know if there are any better ways
?

Thoughts appreciated.

Steve

To determine a solution, you need to describer the rest of your business requirements, such as latency, allowable down time, etc.

|||

Thanks Greg;

Allowable downtime is like most places; none really. Latency, in terms of network, it's not the best, 300ms, but data latency, as long as it's there for the start of the next working day, then there isnt really a problem.

Cheers

|||I suggest reading this High Availability topic in Books Online first. If it doesn't answer any of your questions, then post back here.|||

Good technologies there, trouble is, we are using SQL2000 for our Accounts server.

We dont plan to move to SQL2005 for a while yet, so that rules out DB Mirroring.

Only other option I see are Replication (Which I want to use, but having issues with it) and Log Shipping, but the trouble with this is that the servers are on different, non-trusted domains, which could make that a little tricky?

Thanks for your help.

|||

try using separate a reporting tool over the web. send me an email and i will explain. tony.w@.lycos.co.uk

No comments:

Post a Comment