Skip to main content

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.



Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure” I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps. Remove all relevant namespace files from data-file route path.. Now repair mongo instance using mongod process. mongod --repair ////////// execute command from bin folder path  Then start server using mongd process, if started server successfully then .. mongod  ////////// execute command from bin folder path Restore last backups as normal process. Now check database by connecting mongo shell. Thanks for reading,  Please comment your experience if you faced and also share knowledge if you have better steps to resolve...  

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally

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