Seperate Audit Trail / Scheduling / EDI Databases

[Samanjith]

We are setting up a Multisite environment using SyteLine 6.01.00. When setting up the database there are options to choose whereby you indicate, if you need to have seperate databases for Audit Trail, Scheduling & EDI etc. Our search to find out what are the pros & cons of checking these options has not produced any meaningful answer so far. If anyone would let us know what benefits can be using these additional databases.

 

[Daved0331]

I use a custom Audit Trail package for Windows-based Progress databases. The package was recently enhanced to also work with Unix-based Progress databases. It allows you to track changes to any Progress table and field. Provides table and field, audit date/time, terminal id/PC name, network user id, application user id, program stack, old/new values and more.

Let me know if you want more info...