A new company database should first have been registered and configured by using the installation program. Read more about this in the Company Databases chapter in the MONITOR Basics - Configuration and Maintenance.Why Use This Procedure?
This procedure is used to synchronize new company databases to be used as test or historical companies. Basic data will then be transferred to the new database.
A new company database should first have been registered and configured by using the installation program. Read more about this in the Company Databases chapter in the MONITOR Basics - Configuration and Maintenance.
In the window you then select the new company database that is to be synchronized. During synchronization, you copy basic data from a register in the actual company's database over to an empty database in a new database directory. During the very first synchronization, you should include all the tables. Afterwards, you can also synchronize records or entries from an individual table, for instance if many new parts have been entered in the regular company’s database, and you want to copy these to a previously configured test company.
Historical Registers
In connection with the turn of the business year, we recommend that you create a historical register for the previous year and synchronize this for each company. Once a historical register has been synchronized, you can transfer all the order records that have status 9 (Historical) from the real or "actual" company.
You usually determine how long the interval should be before you transfer historical orders, depending on how intensely the system is used, or how many orders that are created each year. If you have considerable order registrations during each business year, you may choose to transfer these every six or twelve months. If you do not have that many order registrations, you may only need to transfer historical orders every two years or so. This should be decided on a case-to-case basis. The most common practice is to start each new year by creating and synchronizing a new database for a historical register for the previous year, and then purge the actual company from all historical orders, which are transferred to that year's historical register.
The reason you should create historical registers is to avoid having many historical orders (i.e. old or past orders) taking up space in the actual and up-to-date company. If you have too many orders, it usually takes much longer to load your order lists, since searching large order registers becomes very slow. At the same time, having too many old orders left in the system makes it more difficult to analyze and review. It also has a statistical value, for example, in order to make post-calculations on old orders for making price comparisons.
Once a historical register has been synchronized, you can go ahead and transfer historical orders from the actual company to the historical register. This is done in the Purging Procedures procedure.
Test company
In many cases, it may be very useful to configure a test company containing only basic data in its database. This means that the static records (such as parts) will exist in the test company from the very beginning. However, items like the order entries will not be included in the test company.
It may also be useful to update the old basic data in a test company, by running a new synchronization on certain - or all - of the tables in the system.
Window Functions
Read more about the Window functions under Window Functions in the MONITOR Basics guide.