Hello,We have a requirement in our running project that we need to migrate our database(MariaDB on-premise) to MySQL on-premise DB.Currently in our applications we are using CDTs and records and my concerns are- In Appian system, what are the changes we need to do? Is there any impact on existing filters, summary views, and etc. if we change the source of the records? Any impact on existing DSE object? Can you please suggest the impact on any other artifacts in Appian? Thanks!

Question

Database migration from MariaDB on-premise to MySQL on-premise

Forum|Forum|2 years ago
February 9, 2024
9 replies
0 views

Hello,

We have a requirement in our running project that we need to migrate our database(MariaDB on-premise) to MySQL on-premise DB.
Currently in our applications we are using CDTs and records and my concerns are-

In Appian system, what are the changes we need to do?
Is there any impact on existing filters, summary views, and etc. if we change the source of the records?
Any impact on existing DSE object?
Can you please suggest the impact on any other artifacts in Appian?

Thanks!

venkatrea696188

Is there any impact on existing filters, summary views, and etc. if we change the source of the records?

Record connections gonna break and all objects that have record references gonna through an error , Alternative is Create new records with new source and slowly replace the older references.

stefanhelzle0001

Brainy

I suggest to contact Appian to discuss the impact on records. If you modify the database connected system, does that break records using that?

venkatrea696188

does that break records using that?

I experienced this before on Data sync enabled Records ,like whenever i try to change the Data Source or whenever i tried to remove sync and reapply it record's broken . I am thinking same thing gonna apply for database connected system or may be not . Can you give your inputs on it [mention:126a676c85024855948336691b0a7b92:e9ed411860ed4f2ba0265705b8793d05] .

stefanhelzle0001

Brainy

Yeah, when you change the data source of the record, I expect this to happen. I think more about changing the database connection in the connected system, not touching the record.

srmm0001

Update Appian's data sources to point to the new MySQL database.
Check and adjust Custom Data Types (CDTs) for any compatibility issues with MySQL.
Redirect Appian Record Types to fetch data from MySQL instead of MariaDB.
Conduct thorough testing of all Appian interfaces to ensure that filters, summary views, and reports are functioning correctly with MySQL.
Ensure Data Store Entities (DSEs) are correctly mapped to the new MySQL tables.

venkatrea696188

Redirect Appian Record Types to fetch data from MySQL instead of MariaDB.

Hi Srinivas , What does Redirect mean??

srmm0001

"redirecting Appian Record Types to fetch data from MySQL instead of MariaDB" means updating the data source configurations within your Appian application so that the Record Types now point to the new MySQL database tables rather than the old MariaDB tables.

process involves:

Updating Data Source: Changing the JDBC (Java Database Connectivity) URL in the Appian Administration Console to connect to the MySQL database instead of MariaDB.

Modifying Record Type Configurations: Adjusting the Record Type configurations in the Appian Designer to use the new data source which points to MySQL.

Ensure compatibility: Making sure that the structure of the tables in MySQL matches what the Appian Records expect in terms of table names, column names, data types, and any other schema details.

Sign up

Login with SSO

Login to the community

Login with SSO