patternMinor
SSMS 2014 "Deploy Database" feature has old SQL Azure settings
Viewed 0 times
settingsssmssqldeploydatabasehasazureold2014feature
Problem
I'm attempting to test-deploy an existing SQL Server 2005 database into SQL Azure using the "Deploy Database to Windows Azure SQL Database" task in SQL Server Management Studio 2014.
When the wizard launches, it has incorrect (outdated) database settings available:
SQL Azure no longer uses "Web" and "Business" models, and when I try to perform the deployment it fails with the error message
The service objective 'Business' specified is invalid. (Microsoft SQL Server, Error: 40804)
I receive the same error when I attempt to run "Import Data-tier Application" using a .bacpac of my database. The settings are also old for that interface.
It appears SSMS is using an older deployment wizard. How do I correct this?
Edit:
I fired up a SQL Server 2014 VM on Azure and tried performing the same task. I observed the VM version of SSMS has a newer version number (right) than my local copy of SSMS (left):
I see no pending updates from Windows Update, however.
When the wizard launches, it has incorrect (outdated) database settings available:
SQL Azure no longer uses "Web" and "Business" models, and when I try to perform the deployment it fails with the error message
The service objective 'Business' specified is invalid. (Microsoft SQL Server, Error: 40804)
I receive the same error when I attempt to run "Import Data-tier Application" using a .bacpac of my database. The settings are also old for that interface.
It appears SSMS is using an older deployment wizard. How do I correct this?
Edit:
I fired up a SQL Server 2014 VM on Azure and tried performing the same task. I observed the VM version of SSMS has a newer version number (right) than my local copy of SSMS (left):
I see no pending updates from Windows Update, however.
Solution
I wouldn't have been able to find the solution to this problem if you hadn't decided to open the VM on azure and check the version numbers, so thank you!
After I saw your post, I googled "sql 12.0.2430.0" and found a hotfix from microsoft that fixed the problem.
You can find the hotfix Here
The update added full support for the new Azure SQL database tiers.
Cheers!
After I saw your post, I googled "sql 12.0.2430.0" and found a hotfix from microsoft that fixed the problem.
You can find the hotfix Here
The update added full support for the new Azure SQL database tiers.
Cheers!
Context
StackExchange Database Administrators Q#93168, answer score: 9
Revisions (0)
No revisions yet.