We use replication server for advanced queries also. I then use external
BAQs pointing at the replicated SQL data, reducing the load on the
production server.
We replicate every 10 seconds and in seems to work very well for ad-hoc
reporting.
However, AFR replication always seems to generate errors.
BAQs pointing at the replicated SQL data, reducing the load on the
production server.
We replicate every 10 seconds and in seems to work very well for ad-hoc
reporting.
However, AFR replication always seems to generate errors.
On Thu, Jan 3, 2013 at 10:49 AM, Joe Rojas <jrojas@...> wrote:
> **
>
>
> We use Replication server to run complex queries and for reporting.
>
> We replicate our Epicor data (Progress) every 10 minutes. You can choose
> the interval but real-time is not an option.
>
> I not sure what you mean by "replace my call to Epicor business objects
> with SQL queries".
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of tkoch77
> Sent: Thursday, January 03, 2013 9:44 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Replication Server
>
> Hi all,
>
> To cut back on license usage with external applications that are
> accessing Epicor data for read-only purposes, I am wondering how the
> Replication Server works.
>
> How often does the Epicor database replicate to the replication
> database? Because it is replicated to SQL I can replace my call to
> Epicor business objects with SQL queries? Are there any downfalls to
> using the replication server?
>
> Thanks for any insight,
> -Ted
>
> Joe Rojas | Director of Information Technology | Mats Inc
> dir: 781-573-0291 | cell: 781-408-9278 | fax: 781-232-5191
> jrojas@... | www.matsinc.com Ask us about our clean, green and
> beautiful matting and flooring
>
> This message is intended only for the individual named. If you are not the
> named addressee you should not disseminate, distribute or copy this e-mail.
> Please notify the sender immediately by e-mail if you have received this
> e-mail by mistake. Please note that any views or opinions presented in this
> email are solely those of the author and do not necessarily represent those
> of the company.
>
> [Non-text portions of this message have been removed]
>
>
>
[Non-text portions of this message have been removed]