Hi Eshwar,
In general it's recommended to change only one major component at a time (either the major release or the database vendor) to reduce risk. Using a copy of your production database will allow you to test the process extensively upfront. Since you are migrating from Oracle to MS-SQL case sensitivity should not be an issue.
factors to consider:
*) migrate all data at once or client by client
*) is it sufficient to move objects only or is it necessary to also migrate messages, statistics and reports
*) how long is the maintenance window
migration options:
1) DBUnload/DBLoad objects only
2) DBUnload/DBLoad full database
3) ClientCopy Utility
Regards, Markus
Original Message:
Sent: Nov 24, 2023 07:26 AM
From: Purneswara Rao Konda
Subject: Automic DB migration from SQL SERVER to Oracle
Hello community,
We are planning to upgrading Automic from one version to another version at the same time migrating AE DB from SQL Server to Oracle. However we found there are challenges and Broadcom doesn't support for DB migration of there are any issues. So did any one performed similar kind of migration if yes what is success factor and what kind of remediation actions we need to take before doing migration? Please suggest!
------------------------------
Regards,
Eshwar
------------------------------