In this stage, you must run a 'Health Checker' on the Pegasus Opera 3 (Visual Foxpro database) or Opera 3 SQL data and migrate the data to Opera 3 SQL SE using the Migrate company view in Server Administration & Monitoring.
Pegasus Opera II data must first be migrated to either Opera 3 (Visual Foxpro database) or Opera 3 SQL before it can be migrated to Opera 3 SQL SE.
The company data is copied followed by any associated files (for example, statements and remittances).
A 'Health check' must be done before the migration.
A new company is created automatically in Opera 3 SQL SE by the migration.
If a problem is found during the migration the changes in Microsoft SQL Server can be rolled back.
If companies are linked to other companies (for example, Sales Ledger in company A is linked to the Nominal Ledger in company B), all those companies must be migrated together.
Option |
Description |
|---|---|
| System data | Relevant company records from the companies table (SEQCO),
plus the following tables:
|
| Company data | All company data apart from spool files
The migration includes files saved by Opera in a Windows folder - like statements and remittances. These are migrated to the Opera 3 SQL SE Repository or to the 'Migration' folder below the 'Common' folder. |
The 'Migration' folder below the Opera 3 SQL SE 'Common' folder is used for files from the source company that do not have an equivalent folder in Opera 3 SQL SE. Examples are emails and spool files. Please check that folder after the migration.
The root migration folder on the server is 'C:\ProgramData\Pegasus\O3 Server SE\Common\Migration'. A folder is created for each system and company beneath 'Migration'.
The company data must be 'health checked' before the migration. This is important because the database rules in Opera 3 SQL SE are stricter than Opera 3 (Visual Foxpro database) or Opera 3 SQL.
All checks are advised.
Mandatory checks |
Example |
|---|---|
Valid numeric rule |
A numeric overflow; a value of 100 has been added to a field which can only store the maximum value 99. A decimal place numeric overflow; a value of 999.9 has been added to a field which has been defined as 99.99. |
Valid date rule |
Dates prior to 01/01/1753 will error as they are not allowed in Microsoft SQL Server. Warnings are shown for dates prior to 1899. |
Minimum value rule |
Checks that fields do not contain values less than the defined minimum value if one has been defined. |
Maximum value rule |
Checks that fields do not contain values greater than the defined maximum value if one has been defined. |
Optional checks |
Example |
Named value rule |
A field entry is one of the list of specified values; for example, for a sales transaction type is it 'I' (invoice), 'C' (credit note), 'A' (adjustment) and so on. |
Pattern matching rule |
Entries must match a particular pattern; for example, a document reference must match 'XXXX9999' (where XXXX is a letter and 9999 is a number). |
Mandatory value rule |
A field must not be empty; for example, a customer record must have an account number. |
Unique value rule |
Checks that field entries are unique in a table if the field is defined as must be unique. For example, within the customer table, the customer code must be a unique. |
Referential integrity rule |
Checks table joins. Do child records have a parent record? For example, does a invoice transaction record have an invoice header record? |
All actions for stage 1, stage 2, stage 3 and stage 4 must be completed. You should also consider completing stage 5.
To migrate data the Microsoft OLE DB Provider for Visual FoxPro 9.0 must be installed on the server. If required, download it from www.microsoft.com/en-us/download/details.aspx?id=14839.
Access to the Opera 3 (Visual Foxpro database) or Opera 3 SQL data.
Read/Write network permissions to the 'O3 Server SE' folder in the
'ProgramData' location on the Opera 3 SQL SE
server (\ProgramData\Pegasus\O3 Server SE).
This will provide the Read/Write network permissions to the sub folders
in this location that are needed during the migration. After the migration
the Read/Write permissions for the Windows user account must be removed.
Follow these instructions.
This process will take some time to complete.
Make sure that the folders from which the data will be migrated do not include any non-standard Opera 3 files and folders. The migration may fail if non-standard Opera 3 files and folders are found.
Run the Server Administration & Monitoring application using the Windows shortcut on the desktop.
On the Migrate
company view under Database,
do the following:
Under Source:
Select the Opera 3 (Visual Foxpro database) server dynamic folder or Opera 3 SQL server dynamic data folder, for example; C:\ProgramData\Pegasus\O3 Server VFP or C:\ProgramData\Pegasus\O3 Server SQL.
Select a system code if relevant.
Select one or more companies to migrate.
Under Destination:
Select the SQL Server for the new Opera 3 SQL SE database.
Leave the Repository and Common folders as the default.
Under Options:
Leave the Migrate system data, Migrate associated users and Migrate reports options selected.
Leave the Roll back changes if migration fails option selected.
Select all the Health Check options.
Click the Migrate button.
Check the Migration folder for files that were migrated to that location.
After the migration, you must remove the 'Read/Write' network permissions to the 'O3 Server SE' folder in the ProgramData location for the Windows user account used for the migration.
You are now ready to use Opera 3 SQL SE.