ConnectALL database to PostgreSQL migration FAQ
Article ID: 427860
Updated On:
Products
Issue/Introduction
Recently Broadcom announced the end of the support for other databases than Postgres for ValueOps ConnectALL.
This documents covers the Frequently Asked Questions (FAQ) about the migration process.
Environment
ConnectALL 3.7 and above
Database Platforms Affected
- Microsoft SQL
- MySQL
- Oracle
Resolution
Q: Why are we making this change?
A: Broadcom is discontinuing support for Oracle, Microsoft SQL, and MySQL databases used by ConnectALL to focus development resources on new technology and software, as announced below:
Subject: End of Support Announcement for specific databases.
Broadcom is continually working to improve our software and services to best meet the needs of our customers. In order to focus our development efforts and to help our customer base achieve their strategic business initiatives, we are investing our resources in new technology and software and will, effective immediately, be discontinuing support of the following databases used by ConnectALL: Oracle, Microsoft SQL and MySQL. We will continue to support Postgres for ConnectALL.
Q: What are the benefits of this change?
A: Managing multiple database platforms requires developers to be proficient in writing queries, optimizing indexes, and writing upgrade scripts for each platform. Additionally, our QA team is required to write test plans, ensure that upgrades function across all platforms and from a variety of versions. Converging on a singular database platform means that the development and QA teams are able to focus efforts on ensuring better performance and stability. This also aids the support team in being able to resolve issues expediently.
Q: What version of ConnectALL will no longer support non-PostgreSQL databases?
A: Any new installations will only support the Postgres database. Upgrades will continue to support non-Postgres databases up until the ConnectALL 4.5 version.
Q: What version of PostgreSQL is required?
A: Postgres 17 and above
Q: Can we migrate to Postgres but stay on our current version of the software?
A: This depends on your current ConnectALL version. Older versions saved configurations in the filesystem, whereas the latest versions save them in the database. At a minimum, you must be using version 3.7 or higher.
Q: Will there be any dependent activities that need to be completed prior to migration?
A: Yes there may be some additional activities like needing to purge some tables, ConnectALL upgrade or Database upgrade if not supported. Support will be able to evaluate that after the initial meeting to understand the environment.
Q: Will there be any downtime during the migration?
A: Yes, services must be stopped while the migration runs. This typically takes 30 minutes to 1 hour, but may take longer for larger databases.
Q: Will data synchronisation continue normally after the downtime?
A: Yes.
Q: What if the migration fails midway?
A: Simply rerun the migration. The migration process only affects the target database, overwriting existing data on a rerun. The source database is only read from during the process. No data is lost.
Q: What is the backout plan?
A: No need for a backout plan as migration does not affect existing ConnectALL instance. It is just used for reading.
Q: Who needs to be involved in the migration?
A: The Customer DBA and IT personnel with administrative access to the ConnectALL Server.
Q: How will the migration be coordinated?
A: Support will open a case and schedule an initial meeting with your team to begin detailed discussions about the migration.
Q: Will support assist us with this?
A: Yes, we will work with you every step of the way.
Q: What do we need to do to make this change?
A: Support will work with you directly and walk you through every step.
Feedback
