PS - just for clarification - i was speaking about the PERFORMANCE EFFECT of the replication process - as being negledgleible (pardon my spelling) :)
--- In vantage@yahoogroups.com, "erp07052" <erp07052@...> wrote:
>
> Replication to a SQL data base in the installations that i've seen is negledgible - and i would recommend it (the sql db and epm) be setup on a separate server. As does Epicor. You can setup the replication to be as frequent as possible - but typically once or twice a day seems to be very sufficent to all my customer installs.
>
> Also note: be cautious with the setup of REPLICATION PROFILES and take care to not TURN OFF the STD EPM profile, IF you are planning on using the EPM product. There's necesssary - but hidden - tables in the EPM profile that aren't in a "ENTIRE DB" profile.
>
> --- In vantage@yahoogroups.com, "domareddy" <domareddy@> wrote:
> >
> > Hi All,
> >
> > We are currently using Progress database for Epicor9(9.05.604) and would like to implement the Epicor9 Replication (i.e. Replicating the data from Progress to SQL) and use the SQL database for EPM and also as a reporter server
> >
> > What is the performance impact on the production server with this replication, did you all experience any other issues with this Replication.
> >
> > Thanks,
> > Doma Reddy.
> >
>