FAQ
Migration planning
Make sure you have enough disk space for the migrated databases, backups, as well as future database growth. You can use PostgreSQL Assistant to estimate the database size after migration. Each backup requires disk space equal to the total size of all databases, including test databases. Please note! When a new backup is being created, you temporarily need space for both the new and the previous backup.
It is recommended to store the backup on a different disk from the one hosting the database files.
Example:
If the database is 100 GB, you should have at least 350 GB of free disk space available:
-
100 GB for the database
-
250 GB for the backup (database size × 2.5)
During periods of high database activity, the WAL volume may grow to the same size as the database itself or even exceed it.
Tips for saving disk space:
-
Before migrating, review which test companies you still use and need to migrate.
-
Consider exporting BLOB data if you have larger databases.
-
After migration, review your SQL Anywhere production databases and backups to identify any that are no longer needed. Where appropriate, move, compress, or delete them to free up disk space. Learn more about Database cleanup.
Yes. This is especially recommended for large databases. A BLOB export can reduce the database size, lower storage requirements, and speed up migration. For assistance with exporting BLOB data, you can contact our Technical Support team or read more here.
No. You can migrate companies in stages. For example, you can migrate a test company first and keep the other companies in SQL Anywhere until you are ready to migrate them.
Yes. The migration tool checks whether Monitor is running and, if necessary, prompts you to stop the Monitor Server service. The service must remain stopped throughout the migration. The downtime affects all companies in the system, even if only one company is being migrated. Inform all users in advance about the planned migration and that Monitor will be unavailable until the migration is complete.
Yes. Downtime is required even when migrating a test company so that the migration can be completed correctly and without the risk of data corruption.
Yes. Different companies can operate in parallel using different database engines. This means that one company can be migrated to PostgreSQL while another continues to use SQL Anywhere.
Yes. Once the migration is complete, you should be able to start and use Monitor as usual. Users should not normally notice any difference in the client.
Server and database configuration
Yes. PostgreSQL can be installed on a separate database server. In this setup, PostgreSQL must be installed manually on the database server, and the Monitor server must be able to connect to it. Depending on your configuration, you may also need to allow the Monitor server's IP address in PostgreSQL's pg_hba.conf file.
For instructions on how to configure separate application and database servers, see Using separate servers for PostgreSQL.
PostgreSQL is installed on the database server. You then use PostgreSQL Assistant, which is included with the Monitor application server, to connect to the PostgreSQL installation on the database server.
The databases are stored in the PostgreSQL data directory selected during installation. Database management in PostgreSQL differs from SQL Anywhere and should be performed using pgAdmin or a similar database administration tool rather than by managing files directly in the file system.
Integrations, customizations, and database access
No. The API models and endpoints are not affected by the migration. Integrations that use only the Monitor API should therefore continue to work as usual.
Monitor BI should continue to work as before. However, you need to review any custom solutions that read directly from the database, such as custom dashboards that use SQL or external integrations with direct database access.
Custom document and report variants are carried over during the migration. However, if they use custom data sources or SQL queries, you need to verify that they work with PostgreSQL. We therefore recommend testing them in a migrated test company well in advance of the production migration.
Table names, relationships, and column names are generally the same, but SQL syntax differs between SQL Anywhere and PostgreSQL. Custom SQL queries may therefore need to be reviewed and adapted.
Troubleshooting
If the migration fails, an error message is displayed at the top of the migration window. More information about the error can be found in the PostgresMigrator log under Logs. You find the logs here: [Local Monitor installation path]\Monitor ERP System AB\Logs\PostgresMigrator.log.
Contact our Technical Support team if you need help troubleshooting an error.
If the migration appears to have stopped, check Task Manager to see whether the migration process is still running.
If you have canceled the migration or closed the migration window before the migration was completed, the incomplete databases must be manually removed from PostgreSQL. You must also manually ensure that Monitor can reconnect to SQL Anywhere before attempting the operation again. Please contact Technical support for assistance.
The existing SQL Anywhere database is not modified during the migration. If the migration fails, the existing database remains available, allowing you to return to SQL Anywhere.
Contact our Technical Support team if you need assistance restoring or verifying the environment before continuing.
The percentage shown in the progress bar represents the migration steps completed, rather than the elapsed time. Some steps can take significantly longer than others, which means that even the final few percent of the migration may take some time to complete.
If the migration is taking significantly longer than expected, check the following:
-
Antivirus software: Check whether antivirus software is scanning the directories or files used during the migration.
-
Large amounts of BLOB data: Large amounts of BLOB data can increase the migration time.
-
Available memory: Make sure that the server has sufficient available memory to complete the migration.