<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Database migration from MariaDB on-premise to MySQL on-premise</title><link>https://community.appian.com/discussions/f/data/34004/database-migration-from-mariadb-on-premise-to-mysql-on-premise</link><description>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</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Database migration from MariaDB on-premise to MySQL on-premise</title><link>https://community.appian.com/thread/129276?ContentTypeID=1</link><pubDate>Fri, 09 Feb 2024 10:31:32 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:a882e299-1143-4034-a9ca-83831e185ad3</guid><dc:creator>SRINIVAS M</dc:creator><description>&lt;p&gt;&lt;em&gt;When redirecting Appian Record Types to a new MySQL database, you should consider the following impacts:&lt;/em&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;em&gt;Record Query Rules: Update any database-specific syntax in your record query rules to be compatible with MySQL.&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Field References: Check that all fields referenced in interfaces and processes match the new MySQL schema.&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;User Filters: Verify user filters in interfaces work with MySQL and adjust as necessary.&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Data Types: Confirm that data types are consistent between MariaDB and MySQL, as discrepancies can affect data display and logic.&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Database Functions: Replace or rewrite any database functions that do not directly translate from MariaDB to MySQL.&lt;/em&gt;&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Database migration from MariaDB on-premise to MySQL on-premise</title><link>https://community.appian.com/thread/129274?ContentTypeID=1</link><pubDate>Fri, 09 Feb 2024 10:22:04 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:1196c961-d7c4-44a2-91bd-b0510498e46c</guid><dc:creator>mohits1040</dc:creator><description>&lt;p&gt;Hello &amp;nbsp;,&lt;br /&gt;&lt;br /&gt;By redirecting the record type to newly mapped MySQL DB,&amp;nbsp;is there any impact on record query rules,&amp;nbsp;referenced record type fields in all places like interfaces, user filters etc?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Database migration from MariaDB on-premise to MySQL on-premise</title><link>https://community.appian.com/thread/129273?ContentTypeID=1</link><pubDate>Fri, 09 Feb 2024 10:13:36 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:4c3ec643-e6ac-4e6d-89ce-4ffc32cd3872</guid><dc:creator>SRINIVAS M</dc:creator><description>&lt;p&gt;&lt;span&gt;&amp;quot;redirecting Appian Record Types to fetch data from MySQL instead of MariaDB&amp;quot; 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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;process&amp;nbsp; involves:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;strong&gt;Updating Data Source&lt;/strong&gt;: Changing the JDBC (Java Database Connectivity) URL in the Appian Administration Console to connect to the MySQL database instead of MariaDB.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;strong&gt;Modifying Record Type Configurations&lt;/strong&gt;: Adjusting the Record Type configurations in the Appian Designer to use the new data source which points to MySQL.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Ensure compatibility:&amp;nbsp;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.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Database migration from MariaDB on-premise to MySQL on-premise</title><link>https://community.appian.com/thread/129268?ContentTypeID=1</link><pubDate>Fri, 09 Feb 2024 10:04:20 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:9baec055-0436-4a9a-bd71-737e6a382fd8</guid><dc:creator>venkatrea696188</dc:creator><description>[quote userid="244047" url="~/discussions/f/data/34004/database-migration-from-mariadb-on-premise-to-mysql-on-premise/129262"]&lt;strong&gt;Redirect Appian Record Types&lt;/strong&gt; to fetch data from MySQL instead of MariaDB.[/quote]
&lt;p&gt;Hi Srinivas , What does Redirect mean??&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Database migration from MariaDB on-premise to MySQL on-premise</title><link>https://community.appian.com/thread/129262?ContentTypeID=1</link><pubDate>Fri, 09 Feb 2024 09:58:28 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:daa6b0b2-45e0-45b5-8c5b-ce782d016d2b</guid><dc:creator>SRINIVAS M</dc:creator><description>&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Update Appian&amp;#39;s data sources&lt;/strong&gt; to point to the new MySQL database.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Check and adjust Custom Data Types (CDTs)&lt;/strong&gt; for any compatibility issues with MySQL.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Redirect Appian Record Types&lt;/strong&gt; to fetch data from MySQL instead of MariaDB.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Conduct thorough testing&lt;/strong&gt; of all Appian interfaces to ensure that filters, summary views, and reports are functioning correctly with MySQL.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Ensure Data Store Entities (DSEs)&lt;/strong&gt; are correctly mapped to the new MySQL tables.&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Database migration from MariaDB on-premise to MySQL on-premise</title><link>https://community.appian.com/thread/129258?ContentTypeID=1</link><pubDate>Fri, 09 Feb 2024 09:26:18 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:4e7cac35-35f7-4038-9e43-0ca0c3d22ecf</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;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.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Database migration from MariaDB on-premise to MySQL on-premise</title><link>https://community.appian.com/thread/129255?ContentTypeID=1</link><pubDate>Fri, 09 Feb 2024 09:18:51 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:eba90a69-ac66-45de-9a75-ec66203bd47c</guid><dc:creator>venkatrea696188</dc:creator><description>[quote userid="59361" url="~/discussions/f/data/34004/database-migration-from-mariadb-on-premise-to-mysql-on-premise/129249"]does that break records using that?[/quote]
&lt;p&gt;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&amp;#39;s broken . I am thinking same thing gonna apply for database connected system or may be not . Can you give your inputs on it&amp;nbsp;&amp;nbsp;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Database migration from MariaDB on-premise to MySQL on-premise</title><link>https://community.appian.com/thread/129249?ContentTypeID=1</link><pubDate>Fri, 09 Feb 2024 08:45:44 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:162ae9ff-253a-4213-ba40-c7a8d126e2b6</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;I suggest to contact Appian to discuss the impact on records. If you modify the database connected system, does that break records using that?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Database migration from MariaDB on-premise to MySQL on-premise</title><link>https://community.appian.com/thread/129246?ContentTypeID=1</link><pubDate>Fri, 09 Feb 2024 07:22:10 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:38f1635c-3423-43ef-9323-4947b46d6a6b</guid><dc:creator>venkatrea696188</dc:creator><description>[quote userid="268348" url="~/discussions/f/data/34004/database-migration-from-mariadb-on-premise-to-mysql-on-premise"]Is there any impact on existing filters, summary views, and etc. if we change the source of the records?[/quote]
&lt;p&gt;Record connections gonna break and all objects that have record references gonna through an error , Alternative is Create new records with new source&amp;nbsp; and slowly replace the older references.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>