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

mohits1040 said:

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. 

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

Unknown said:

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  .

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.

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

Srinivas said:

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

Hi Srinivas , What does Redirect mean??

"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.

Hello Srinivas ,

By redirecting the record type to newly mapped MySQL DB, is there any impact on record query rules, referenced record type fields in all places like interfaces, user filters etc?

When redirecting Appian Record Types to a new MySQL database, you should consider the following impacts:

1. Record Query Rules: Update any database-specific syntax in your record query rules to be compatible with MySQL.
2. Field References: Check that all fields referenced in interfaces and processes match the new MySQL schema.
3. User Filters: Verify user filters in interfaces work with MySQL and adjust as necessary.
4. Data Types: Confirm that data types are consistent between MariaDB and MySQL, as discrepancies can affect data display and logic.
5. Database Functions: Replace or rewrite any database functions that do not directly translate from MariaDB to MySQL.