Securing Database Access

It is recommended to replicate your ERP Database if you want to be 100 % sure to have no impact on the ERP and also for security reasons.

This scenario can be used in combination with any of the previous four scenarios and presents the following advantages:

• The actual production database of the main data source system does not have to handle Nectari requests, so there is no additional load on the production server.
• Configuring database duplication represents a technical complexity.
• It could be more expensive to deploy and maintain such a configuration.
• There could be performance issues if the Nectari server is not properly sized.
  Note

  In the case of Sage X3 on SQL Server, using DataSync is the recommended way to duplicate the ERP.

  If you intend to use Log Shipping, you must be aware of the following limitations:

  • There is some delay when updating the data, depending on the configured frequency for Log shipping. Therefore, the reporting information is not based on real-time data.
  • There could be potential connection loss on the user interface when the duplicate database is being updated. However, this will be transparent to the users most of the time.

  • If you use OLAP Manager, the Refresh process uses triggers and requires a writable database. Since the Log Shipping database is read-only, Log Shipping is not possible with OLAP Manager because we cannot maintain the tracking tables.