Epicor Database Replication

(I don’t think we’ve actually answered the OP’s question but only given alternatives)

@AmilaAmarasinghe_Str - up until SQL 2016 (I think), you couldn’t actually do replication of Epicor’s database because the SQL replication process balked and having GUID key fields (or something like that). Trust me, I tried it a few times between SQL 2000 and 2014.

In turn, everyone like @Mark_Wonsil, @markdamen and I have developed different ways to provide a DEV copy of the data on demand. You’ve heard about SSIS, PowerShell/REST, and I use good old SQL scripting + a little manual appserver management.

None of these are bad, but more automation is always good. With the new versions of SQL server, you should be able to do a one-direction replication to a DEV server without issue. I might reach out to EpicCare and ask about current replication process/issues. Back a few years you had to run a script to alter some key indices or something in order to make it work, but I haven’t looked into recently.

2 Likes