I am learning azure from Microsoft learn using this link. Does anyone know the basic difference between "Azure Database for MySQL" and "Azure SQL Database"? Both seem very similar.
As I am a beginner, can anyone explain the difference in an easy way?
Add to #CoderRambo's answer. The difference between Azure Database for MySQL and Azure SQL Database is as follows:
Azure Database for MySQL is powered by the MySQL community edition. We can choose versions 5.6, 5.7, and 8.0.
Azure SQL Database is SQL Server database engine, based on the latest stable Enterprise Edition of SQL Server.
The only similarity is: they are all hosted in the Microsoft cloud and fall into the industry category of Platform-as-a-Service (PaaS). So your question is mysql vs sql server.
ok lets start with what is common for both. with Azure prefixed, both are installed in cloud and managed by Microsoft. Meaning Microsoft is responsible for the databases to be installed, up and running with 0 or minimal downtime. I think this is clear.
Now lets start with differences. Please visit the links below and let me know if you have any issues. Thanks!
https://www.guru99.com/sql-vs-mysql.html
https://www.javatpoint.com/mysql-vs-sql
Mysql is opensource database, where as when you say SQL it refers to Microsoft SQL Server.
In general both are two different types of databases. Microsoft SQL Server is a licensed version.
When you prefix them with Azure, it means they are hosted on cloud , i.e Azure cloud and Microsoft manages them as PAAS(platform as a service).
Kindly let me know if you need more information.
Related
Im new to the cloud universe of Microsoft and confused with their Migration Services, so forgive me if this question seems like there was no effort put into finding an answer myself.
Im evaluating to migratre our Sybase ASE 16 environment to the Cloud, preferably to AZURE, because of Sybase and Microsoft both rely on T-SQL for procedural programming. This being said I was looking through the docs and could not find any out of the box cloud migrating solution for Sybase.
Link:
https://learn.microsoft.com/de-de/azure/dms/resource-scenario-status
I understand Microsofts definitions of offline and online migration but neither offer a service for Sybase products. I then stumbled up on SSMA ( Micrsoft SQL Server Migration Assistant for SAP Sybase ASE). From my understanding this is a tool to migrate a Sybase Database to a Microsoft SQL Server Database and has nothing to with AZURE.
But I could have an AZURE DB sitting in the cloud and just use it as the destination for my migration?
Is this best practice for SAP Sybase ASE migrations to AZURE?
Azure offers a migration tool to migrate to the cloud. If you need to migrate a Sybase Database you will need to use Microsoft SQL Server Migration Assistant for SAP.
In order to migrate your Sybase Database you need to download the SSMA Client and the extension pack for your Microsoft SQL Server.
Inside the SSMA you first have to convert selected database schemas, then synchronize them in the bottom database explorer with your destination database and then you are ready to hit the migration button.
Keep in mind that Microsoft SQL Server is case insensitive by default but you can change the case sensivity on a database level for sysdb in Microsoft SQL Server Manager.
Also it is important to point out that this tool only migrates DDL but not users and permissions.
I have read many articles but i cannot be confirmed if linked server is supported in SQL Azure DB(PAAS)environment? I read somewhere that it is applicable only in hybrid environments.
Can anyone please confirm if linked server can be used with databases in azure and not just in hybrid?
Linked server are not supported in SQL Azure; you can only create a linked server in an on-premise SQL Server to a SQL Azure database.
reference link : https://social.technet.microsoft.com/Forums/en-US/1943b51b-151d-4510-9bbd-ceb6b51bde3b/sql-azure-linked-data-base
we discover that the Microsoft Sql Azure Web databases are going to retired in the September 2015.
our application (PHP application) is working on federation mechanism.
how to convert our federation to the new elastic scale out?
is there is a new Sql federation command to create new federations and control them?
is there is an easy way to move data smoothly from the federation mechanism to the new scale out (Web to Basic) databases?
there's no SQL command for doing the migration, the migration steps and a migration utility is available at this link. You will have to do some code changes on your app as well.
The new Elastic Scale features in Azure SQL DB are provided through client libraries that currently are available only with ADO.Net. A complete summary of capabilities can be found at this link. Included are tools that allow migration from federations "in-place". However direct PHP api support is not currently available. I would like to understand your scenario better so please email me directly -- stuarto (at) Microsoft (dot) com.
My web project uses an software, which need to be installed on destination PC. So, I have to use Azure VM and no way to use Azure Cloud Service, right?
Also, can I use SQL Azure with Virtual Machine?
You can install any third party software on Azure Web/Worker roles (Cloud Services), as long as the installer supports a quiet/unattemded install from a command line with switches. Learn more how to do this via StartUp tasks here.
As for Azure SQL Database - you can use with any combination of services. Even with on-premises only solution. You have to take care of Firewall rules.
Azure SQL Database tends to be much less expensive than a VM with SQL Server installed. It won't run on a VM but you can access an Azure SQL database from an VM or web application in the same way you access local databases - You just set the connection string to the Azure SQL connection string.
There is an excellent post that can help you with in order to understand how to configure customization with cloud services.
microsoft-azure-cloud-services-part-4-lifecycle-and-customization-of-your-vm
As the link explains there is nothing persisted on a cloud service VM but this is not a limitation instead a good practice which allows easy scaling out by adding more instances if required.
You can use Azure PaaS SQL just like a SQL server installed on a different server then your web server with some limitations. Please have a look at the link below from MSDN to understand these limitations.
sql-database-transact-sql-information
I have a BizSpark account and I get some Azure freebies from Microsoft. But, I'm forced to create a live SQL Azure database to use in my local development. This slows me down a bit because I have to read/write over the wire when I'm developing, and I must remain connected at all times.
Is there a way, or a technique, to build locally and have my deployments access the express edition of SQL Server on my machine? I'm using EF4 to access the database.
First of all, as a part of Bizspark, you get 3 SQL Azure databases for free. http://msdn.microsoft.com/en-us/subscriptions/ee461076.aspx
This will allow you to have 1 DB for testing, 1 for dev, and 1 for production
If this does not work out for you, you CAN develop on your local SQL Express and keep deploying your changes to SQL Azure as you deploy your application to Azure. There are two tools that help you here:
1) open-source SQL Azure Migration Wizard: http://sqlazuremw.codeplex.com/ -- we personally do not use this for deployments, so I am not super knowledgeable to comment on this. It is a decent tool to back your SQL Azure database.
2) You can use Red Gate's SQL Compare product, as of v9.0+, they support synchronizing cross SQL Azure and on-prem SQL servers. We use this for AzureWatch and are very happy. It is commercial product and is somewhat pricey.
HTH
+1 to Igorek's answer - plenty of good suggestions there.
In addition to his advice, if you are a BizSpark licensee then I suggest you deploy full SQL Server 2008 R2 to a local box and develop against that.
There are differences between full SQL Server and SQL Azure - you should read around to be aware of these - http://social.technet.microsoft.com/wiki/contents/articles/comparing-sql-server-with-sql-azure.aspx
As long as you are aware of the differences (especially the SQL Azure limitations) then migrating back to SQL Azure later, should be reasonable.