SQL Server 2014 Management Studio - updated support for the latest Azure SQL Database Update V12 (preview)

We are excited to announce enhanced SQL Server 2014 Management Studio (SSMS) support for Azure SQL database including the latest SQL Database Update V12 (preview). Bringing this functionality into SSMS provides an easy way to discover and better leverage cloud capabilities in a familiar environment. Available for download now, this functionality is being delivered via the SQL Server CU5 update.

 

What’s New

We’ve enabled a variety of scenarios to fill some existing gaps in our Azure SQL database experience. These range from added support for the Database Properties dialog and Table Designer to command availability in the Object Explorer. Additionally, the Import Export and Deploy to Azure wizards have be extended to support the latest SQL Database Update V12 (preview). Let’s take a look at some
of the things we’ve brought into this update.

 

Database Property Dialog

The properties dialog has been extended to add support for the performance model for Azure SQL Database. You can now view and change your Service Tiers (Editions) as well as Performance Levels (Service Level Objectives). For more details on the performance model, see Performance Levels and Service Tiers.

 
 

 

Object Explorer

Several new contextual menu items are now enabled for Microsoft Azure SQL Databases that are outlined below.

 

Table Designer

Now you’ve got access to a powerful productivity surface in SSMS with the added support of the table designer for Azure SQL Database. Some tasks are suited for T-SQL, others for the designer. You can now choose the method you’d like to accomplish the work across a range of platform offerings.

 

 “Select Top 1000 Rows” and “Edit Top 200 Rows”

In terms of utility, we’ve added support for quickly showing the top rows of a table in Azure SQL Database. This is one of those little things that make DBA and development work just a bit easier.

 
 

 

Table Properties Dialog and Sequence Dialog:

Reviewing and setting the myriad of properties on a table is sometimes easier with some help from a familiar user interface. Table properties and sequence dialogs are now supported for tables in Azure SQL Databases.

 

Extend Object Types in the Object Explorer

The Object Explorer has been updated to properly display the supported object types in Microsoft Azure SQL Databases. The new exposures here includes: Aggregate Functions, Application Roles, Assemblies, Columns/Indexes for Tables, Defaults, Plan Guides, Rules, Sequences, Storage, User-Defined Object Types, and XML Schema Collections. This represents a significant growth in surface area for Azure SQL databases – as the surface area moves closer to SQL Server, managing and maintaining these objects just like SQL Server makes good sense.

 

 

Functions and Stored Procedures

The context menu commands for Functions and Stored Procedures have been exposed properly for Azure SQL Databases.

 

Open in Management Portal…

The “Open in Management Portal…” option for Azure SQL Databases we’ve added allows direct navigation to the Azure Management Portal. This provides an easy way of accessing your Azure SQL Databases in the Azure portal.

 

 

Contact Us

If you have any questions or feedback, please visit our Microsoft Connect page. We look forward to hearing from you.

 

SQL Server team

Comments

  • Anonymous
    December 22, 2014
    What's with the obnoxious hotfix download process?

  • Anonymous
    December 22, 2014
    Hi, great news, especially for the feature of table designer. I tried to install the hotfix, but the management portal does not show me the new features. Is there any constraint to get it ? Thanks Fabio

  • Anonymous
    January 02, 2015
    The comment has been removed

  • Anonymous
    January 05, 2015
    Hello Fabio, These features are only going to be present with SSMS connecting to Azure v12.  Can you validate the server version of Azure you are connecting to? Hello Ivan, This is a known issue and we are working on getting this straightened out.  Sorry about the inconvenience.  At this time, you will not be able to see the database properties in Azure v12 until SSMS uses a different method or the Azure v12 service is updated to allow dbo.slo_database_objectives. Thanks, Matt Jones SQL Server Tiger Team

  • Anonymous
    January 08, 2015
    Should foreign keys be editable with the table designer on Azure? The error is "Failed to retrieve data for this request.  Unknown property IsAccessible"

  • Anonymous
    January 22, 2015
    Hello James, Thank you for submitting this feedback. We are investigating the issue and will update you when we have more information. Matt Jones SQL Server Tiger Team

  • Anonymous
    January 28, 2015
    Hello Everyone, Thanks again for your feedback and support.  You can download the fix for the database properties window connecting to Azure v12! http://hotfix/search.aspx?search=3032087 Thanks, Matt Jones SQL Server Tiger Team

  • Anonymous
    January 28, 2015
    Hello again, Here is an easier location to retrieve the hotfix! support.microsoft.com/.../en-us Thanks, Matt Jones SQL Server Tiger Team

  • Anonymous
    January 30, 2015
    Hi Matt, I've installed both hotfixes, and unfortunately I can still not access any of the new UI functions for SQL Azure v12 databases (such as table designer, select top 1000 rows, etc). I have confirmed with two different database servers that have SQL Azure v12 on them. Are there any troubleshooting steps I can do to get this functionality to work? Thanks. Thanks, Tommy

  • Anonymous
    February 05, 2015
    Trying to download the hotfix but once the email comes in with the link and I click it I get a 500 error.  I'll try again later but thought I would let you know in case you can nudge someone.

  • Anonymous
    February 05, 2015
    Hotfix download link is broken for me as well:  "500 - Internal server error".

  • Anonymous
    February 07, 2015
    I installed the hotfix announced Jan28 but it still hasn't fixed the IsAccessible message when editing table relationships.

  • Anonymous
    February 09, 2015
    Hello James, We have not identified a fix for the "IsAccessible" issue yet and are still looking into it.  I will post on this thread when we find and create a fix. Thanks, Matt Jones SQL Server Tiger Team

  • Anonymous
    February 09, 2015
    Hello Tommy, Can you verify the version being reported by the server? SELECT @@VERSION AS 'SQL Server Version'; As for the HTTP 500 error, please verify the content is not being blocked.  The link is to an executable (EXE), so you might need to add http://hotfixv4.microsoft.com to your trusted sites list. Thanks, Matt Jones SQL Server Tiger Team

  • Anonymous
    February 11, 2015
    I can confirm that the hotfix mentioned in the thread does not fix the issue with access to any of the new UI functions for SQL Azure v12 databases (such as table designer, select top 1000 rows, etc). http://hotfix/search.aspx?search=3032087 KB Article Number(s): 3032087 Here is the results when I run the SELECT @@VERSION AS 'SQL Server Version'; Microsoft SQL Azure (RTM) - 11.0.9229.22 Jan 19 2015 17:56:57 Copyright (c) Microsoft Corporation Has anyone been able to get the new GUI features with SSMS 2014 working?? Please let me know if you need anymore information. Thanks Sean

  • Anonymous
    February 22, 2015
    Matt - thanks for responding, I ran the query, and I get: Microsoft SQL Azure (RTM) - 12.0.2000.8 Feb 21 2015 12:12:19 Copyright (c) Microsoft Corporation What is interesting is I recently ran the hotfix on my desktop, and the new SSMS features worked. On my laptop, the features do not work. I decided to try uninstalling SQL 2014 on my laptop - which uninstalled successfully, but did not remove the hotfixes. At this point, I can reinstall SQL 2014, but cannot reapply the hotfixes, which are stuck in a limbo of not actually being installed, but won't let a reinstall fix the state. Is there any solution for this other than reinstalling Windows (which I really would rather not do)? Thanks. Thanks, Tommy

  • Anonymous
    March 02, 2015
    The comment has been removed

  • Anonymous
    March 02, 2015
    Disregard my comment, I missed the comments specifying this was for v12 Azure ... apparently I am still on 11.0.9230.38.

  • Anonymous
    April 21, 2015
    Applied the Hotfix to SSMS. SSMS Version is now: Microsoft SQL Server Management Studio 12.0.2456.0 But it still does not contain a database properties dialog for Microsoft SQL Azure (RTM) - 12.0.2000.8

  • Anonymous
    May 10, 2015
    Do we have an ETA on the IsAccessible bug?

  • Anonymous
    May 12, 2015
    I was looking for this, great, thanks!

  • Anonymous
    May 18, 2015
    what is the version of SQL Server 2014 Management Studio?

  • Anonymous
    May 27, 2015
    After installing CU7 ("SQLServer2014-KB3058512-x64.exe") I still can't see any table columns in SSMS. SSMS version:    12.0.2504.0 OS:    6.1.7601 Azure version:    Microsoft SQL Azure (RTM) - 12.0.2000.8, May 21 2015 21:47:17, Copyright (c) Microsoft Corporation

  • Anonymous
    July 09, 2015
    Does SSMS now allow SQL Profiling of SQL Azure?  Since V12 this is not an option via Silverlight.  If not,  how do you do this now in V12?

  • Anonymous
    July 12, 2015
    What is wrong with that hotfix server? I constantly get Network Errors trying to download the file. Please can you respond, as I apparently glanced over the fact that the Silverlight manager is not working anymore in V12.

  • Anonymous
    July 27, 2015
    Any update on the relationships IsAccessible issue? It's still occurring when I try to setup a foreign key relationship using the designer view. SSMS 12.0.4213.0

  • Anonymous
    July 30, 2015
    I am still receiving this issue as well and the supplied Hotfix in this thread does not work. Any update on a fix?

  • Anonymous
    August 11, 2015
    It really is amazing how such an obvious bug can still not be fixed.   Please advise where it stands on the roadmap.  Having to write relationship SQL statements by hand is frustrating sometimes.

  • Anonymous
    August 19, 2015
    @James I agree with you.  I'm wondering if Azure is worth the trouble given such basic problems.

  • Anonymous
    September 03, 2015
    So this Relationships issue has not been fixed a year later? Coupled with the inability to use Database Diagrams in SSMS to edit relationships with Azure SQL, this seriously makes me question the viability of Azure SQL as a solution. These inane bugs just should not exist.

  • Anonymous
    September 16, 2015
    James - you have not posted on the IsAcceccible issue in a while. does that mean it will not be fixed??

  • Anonymous
    September 22, 2015
    Yes, I too am looking for a response on the IsAccessible issue. Is there an update?

  • Anonymous
    October 08, 2015
    Still no fix on the IsAcceccible issue.... Are we to use SSMS 2015?

  • Anonymous
    October 22, 2015
    Came by to say I too am amazed that there is no built in support for Foreign Key constraints using SSMS's GUI with Azure V12. How can a bug as critical as this even make it into a production release? Will be waiting impatiently for a fix.

  • Anonymous
    October 22, 2015
    It's unbelievable, I can not create foreign key relationships because of that isAccessible issue, and no one can help us here. I'm using the trial version for azure databases, and this is not a good sign for me

  • Anonymous
    October 22, 2015
    What did u do about that is Accesible issue, did u decide to use CodeFirst instead of Database first?

  • Anonymous
    October 29, 2015
    What about the Editor Design Tool ??? most used and do all manual in seconds... PLEASE !!!

  • Anonymous
    November 04, 2015
    It's a been nearly a year and the IsAccessible issue still isn't fixed? I'm still seeing the issue with the latest SQL Server Management Studio 2014.

  • Anonymous
    November 10, 2015
    why not just use T-SQL to avoid the IsAcceccible issue? ALTER TABLE Orders ADD CONSTRAINT fk_PerOrders FOREIGN KEY (P_Id) REFERENCES Persons(P_Id)

  • Anonymous
    December 21, 2015
    The error is "Failed to retrieve data for this request.  Unknown property IsAccessible" This error still persists ..UGH.

  • Anonymous
    January 21, 2016
    Time to look elsewhere for SQL solution :(

  • Anonymous
    March 05, 2016
    the isAccessible issue is still present ... please fix

  • Anonymous
    July 05, 2016
    The comment has been removed