@Praveen Atmakuri I want to ensure the document in the link above will move your on-premise MySQL to MySQL in Azure.Azure Database for MySQL is a Microsoft cloud based service based on the MySQL Community Edition database engine. Advantages Built-in high availability with no additional cost. Predictable performance, using inclusive pay-as-you-go pricing. Scale as needed within seconds. Secured to protect sensitive data-at-rest and in motion. Automatic backups and point-in-time-restore for up to 35 days. Enterprise-grade security and compliance. Difference between Azure MSSQL and Azure MySQL DB MySQL is open source while MSSQL is licensed(commercial). MySQL supports more programming languages than MSSQL MySQL supported several Platforms Windows, Linux and Mac OS while MSSQL runs exclusively on windows though Microsoft recently announced MSSQLwill be available on Linux. MySQL supports a number of storage engines. While using MySQL even have option to use a plug-in storage engine. MySQL does not allow users to kill or cancel a query when it is running But SQL Server programmers can truncate a database query during execution without killing the entire process. These are just but a few distinct differences between the 2 RDBMS's If you found this answer addressed your question, please take a moment to log in and click the "accept" link on the answer. ... View more

@Praveen Atmakuri Here is some info I landed on in some forum 1) "fs.trash.interval" is not respected on blob storage. 2) "hadoop fs -expunge" creates a checkpoint instead of empty the trash Apache documentation on 'fs -expunge' is a little confusing or inaccurate in simply stating it will "Empty the Trash". The command will actually do two things: a) delete all the old checkpoints that are older than the 'fs.trash.interval' config value. b) create a new checkpoint of current Trash directory. For Azure blog storage not respecting 'fs.trash.interval, there is a bug being tracked for this issue. There are some technical difficulties in solving the problem. In HDFS, namenode will enforce the interval config and clean up the Trash according to the config. In Azure blog storage, we don't have an HDFS namenode equivalent component that can enforce the rule. Could you try to set it to 5 minutes and test just for curiosity? ... View more