Azure doesn't support MyISAM engine

Azure DB for MySQL released in the year 2017, this given the new advantages for those customers whose environment is SQL Server along with open source RDBMS. Now cloud database platform changes the technology parameter cutting-edge technology to bleeding edge technology, everything is being crossed platform.

Recently one of the clients has thinking to shift their in-house MySQL to Azure environment. Their 70% database platform is on SQL Server and rest are on MySQL and MongoDB. We got chance to migrate existing database to Azure. The application was 3 years old and database was mix of the plug gable engine of on tables like MyISAM, InnoDB, and csv.

Like all other Azure services MySQL on AzureDB is also easy to setup in few clicks. We did the same but when we started migrating database, it raised the error "Azure doesn't support MyISAM". Actually, Azure did good for Database point of view but for existing system we required to do some changes. We changes the table's engine for those tables having MyISAM and then did migration again. Finally I seen my first MySQL Database on AzureDB.

Thanks

Comments

History of MySQL from AB Corp to Cloud Database

MySQL was created by a Swedish company, MySQL AB, founded by David Axmark, Allan Larsson and Michael "Monty" Widenius. Original development of MySQL by Widenius and Axmark began in 1994. The first version of MySQL appeared on 23 May 1995. Its name is a combination of "My", the name of co-founder Michael Widenius's daughter,and "SQL", the abbreviation for Structured Query Language. · 23 May 1995 - First internal release · Year 1996 - Version 3 o Simple CRUD operations o January 1997 Windows version was released on 8 January 1998 for Windows 95 and NT o production release 1998, from www.mysql.com · Year 2002 - Version 4 o MyISAM o unions o Tracking o B-trees o s...

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription

Configure Impersonation Authentication in IIS8 for MVC Application

Impersonation is when ASP.NET executes code in the context of an authenticated and authorized client. By default, ASP.NET does not use impersonation and instead executes all code using the same user account as the ASP.NET process, which is typically the ASPNET account. There are 5 below steps by which we can establish Impersonation configuration in our secured application environment. 1.) Creation of Application/Proxy user where Application is hosted. 2.) Give appropriate access to the user. 3.) Create Database Login user on database. 4.) Authenticate User and provide credential on IIS. 5.) Then Configure web.config on Application.

The Young DBA

Search This Blog