I have a sql server database running on Azure. Is it possible yet to upgrade this to Sql Server 2017?
I have searched, but only found data on running 2017 in a VM.
I looked in the Portal, but I did not see any option for specifying the version of Sql Server.
"Upgrade" is the wrong word. SQL Azure runs a newer version of SQL than SQL Server 2017. As such, even if were to get the file from SQL Azure (it is not exposed as a feature to do this), SQL 2017 would not be able to open it. (A later version of SQL Server might be able to read it, however). You are welcome to export a SQL Azure database using the Import/Export service to logically copy the database out. You can also use Data Sync or other replication techniques to export the data as it changes.
https://learn.microsoft.com/en-us/sql/relational-databases/import-export/overview-import-export?view=sql-server-2017
https://learn.microsoft.com/en-us/azure/sql-database/sql-database-get-started-sql-data-sync
The closest direct answer is:
It is based on the latest stable version of Microsoft SQL Server database engine.
This is quoted from the first paragraph on https://learn.microsoft.com/en-us/azure/sql-database/sql-database-technical-overview
Additionally, if you are using SSMS 18, or Azure Data Studio, you should be able to change the compatibility level of the database to a higher level such as 150 for SQL Server 2019.
Azure SQL database and AZure SQL Managed Instance use a different versioning than the On- premises product.
For example: Microsoft SQL Azure (RTM) - 12.0.2000.8 Aug 5 2019 05:50:58 Copyright (C) 2019 Microsoft Corporation
The above version is from a Managed instance and Azure SQL also has same version :
As explained by Conor, under the hood it runs the latest possible SQL Server version.
If you want SQL Server 2017 specifically,the you might need to try Azure VM with SQL Server 2017 installed.
As 2019-08-26 Microsoft states the version used in Azure SQL is v12 which corresponds with Azure SQL Server 2014 (source: https://learn.microsoft.com/en-gb/azure/sql-database/sql-database-technical-overview#sql-database-frequently-asked-questions-faq)
It seems we have no upgrade option available.
Related
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.
I am trying to deploy my sql server 2014 database to SQL Azure using SQL Server Management Studio (SSMS) 2014 and i get the following error:
I selected a Business edition while selecting which SQL Edition in the Sql deploy Wizard.
If you're trying to deploy to the Business tier, it's now retired. The wizard may not be updated to reflect this change. The tier that you will want to select for similar performance is probably one of the Standard tiers, but Premium is also available. For more information, view https://azure.microsoft.com/en-us/blog/azure-sql-database-introduces-new-service-tiers/
Upon further checking (see below) it seems that the tools are not upgraded to reflect the current tiers. So the problem is with SSMS in this case.
Can I use SQL Server 2012 on-Premise database with Azure Mobile service(.net backend) for offline Synchronization?
In the following tutorial in prerequisites using SQL Server 2014, cant I use SQL Server 2012.
https://azure.microsoft.com/en-in/documentation/articles/mobile-services-dotnet-backend-hybrid-connections-get-started/
Thanks.
Yes, you can use older versions of SQL Server. The tutorial just assumes SQL Server 2014, so the steps for configuration may be different.
For more information, see the following tutorials:
https://azure.microsoft.com/documentation/articles/integration-hybrid-connection-overview/
PowerShell CmdLets | Hybrid Connection Manager
Recently we have decided to move our old stuff from SQL Server 2012 to Azure SQL server. I have created a SSDT project using 'Import->Database' option and deployed existing database from SQL Server 2012 to Azure Database.
For some reason we must continue to use existing 'SQL Server 2012' database, so our DBA is changing schema on 'SQL Server 2012' database for new business features. In order to make sure that both the schema ( SQL Server 2012 and Azure SQL Server ) I am planning to use 'Schema compare' option. My source is on-premises 'SQL Server 2012' database and destination is 'Azure SQL Server' database.
After finishing comparison I am getting below error.
"A project which specifies SQL Server 2012 as the target platform cannot be published to SQL Azure."
Is there any way for comparing on-premises database with SQL Azure and push changes to Azure db suing SSDT ?
In the Schema Compare window, click the Options button, go to General, and select "Allow incompatible platforms". This will allow you to compare different platforms such as this. Similarly when publishing you can select this in the Advanced publish options.
I would actually recommend setting the target platform for your database project as Azure rather than SQL 2012, as it enforces a more restrictive set of rules than SQL 2012 does at present. You should be able to deploy anything built with Azure validation to SQL 2012, but the same isn't true the other way around. The same "Allow incompatible platforms" setting will work that way too.
I have a web site running in an Azure Cloud Services Web Role, which uses an Azure SQL Database. For development, I use SQL Server LocalDb, which was installed with Visual Studio 2013.
Now that SQL Server 2014 is released, should I switch to its version of LocalDb? Does the new LocalDb provide a more realistic emulation of Azure than the LocalDb that ships with VS2013? If I should switch, what should I uninstall and what should I install? Any other configuration changes?
Microsoft has released an update to SQL Server Data Tools which includes an update to LocalDb. The built-in Visual Studio 2013 Product Updates now includes the SQL Server Data Tools update.