I am having issues after my Azure SQL got updated to version 13.0.15

I am unable to view and browse SQL Stored procedures in Management Studio 

Error I am getting on trying to open Stored procedures in SSMS is:

TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
unknown property IsNativelyCompiled (Microsoft.SqlServer.Management.Sdk.Sfc)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------

My system info as taken from SSMS is pasted below:
Microsoft SQL Server Management Studio 12.0.2000.8
Microsoft Analysis Services Client Tools 12.0.2000.8
Microsoft Data Access Components (MDAC) 6.1.7601.17514
Microsoft MSXML 3.0 4.0 6.0 
Microsoft Internet Explorer 9.11.9600.17728
Microsoft .NET Framework 4.0.30319.18444
Operating System 6.1.7601

I have SQL Express installed and I am able to browse Stored procedures for it, just unable to browse them for Azure SQL

Please help, any help is appreciated

Hi Ivgoran,

Please apply the Cumulative update package 5 for SQL Server and check if it resolves your issue.
Also, if possible you can update the Service Pack, there are somethings that might fail again so best is to update the Service Pack [SP1].

https://support.microsoft.com/en-us/kb/3011055

Regards,

Mekh.

• Edited by Mekh SubbaMicrosoft contingent staff, Moderator 17 hours 14 minutes ago spelling

Hi Ivgoran,

Please apply the Cumulative update package 5 for SQL Server and check if it resolves your issue.
Also, if possible you can update the Service Pack, there are somethings that might fail again so best is to update the Service Pack [SP1].

https://support.microsoft.com/en-us/kb/3011055

Regards,

Mekh.

• Edited by Mekh SubbaMicrosoft contingent staff, Moderator 17 hours 5 minutes ago spelling

Hi Ivgoran,

Please apply the Cumulative update package 5 for SQL Server and check if it resolves your issue.
Also, if possible you can update the Service Pack, there are somethings that might fail again so best is to update the Service Pack [SP1].

https://support.microsoft.com/en-us/kb/3011055

Regards,

Mekh.

• Edited by Mekh SubbaMicrosoft contingent staff, Moderator Friday, April 24, 2015 2:01 PM spelling

Hi Ivgoran,

Please apply the Cumulative update package 5 for SQL Server and check if it resolves your issue.
Also, if possible you can update the Service Pack, there are somethings that might fail again so best is to update the Service Pack [SP1].

https://support.microsoft.com/en-us/kb/3011055

Regards,

Mekh.

• Edited by Mekh SubbaMicrosoft contingent staff, Moderator Friday, April 24, 2015 2:01 PM spelling

Hi Ivgoran,

Please apply the Cumulative update package 5 for SQL Server and check if it resolves your issue.
Also, if possible you can update the Service Pack, there are somethings that might fail again so best is to update the Service Pack [SP1].

https://support.microsoft.com/en-us/kb/3011055

Regards,

Mekh.

• Edited by Mekh SubbaMicrosoft contingent staff, Moderator Friday, April 24, 2015 2:01 PM spelling

Hi Ivgoran,

Please apply the Cumulative update package 5 for SQL Server and check if it resolves your issue.
Also, if possible you can update the Service Pack, there are somethings that might fail again so best is to update the Service Pack [SP1].

https://support.microsoft.com/en-us/kb/3011055

Regards,

Mekh.

• Edited by Mekh SubbaMicrosoft contingent staff, Moderator Friday, April 24, 2015 2:01 PM spelling

Hi Ivgoran,

Please apply the Cumulative update package 5 for SQL Server and check if it resolves your issue.
Also, if possible you can update the Service Pack, there are somethings that might fail again so best is to update the Service Pack [SP1].

https://support.microsoft.com/en-us/kb/3011055

Regards,

Mekh.

• Edited by Mekh SubbaMicrosoft contingent staff, Moderator Friday, April 24, 2015 2:01 PM spelling

Hi Ivgoran,

Please apply the Cumulative update package 5 for SQL Server and check if it resolves your issue.
Also, if possible you can update the Service Pack, there are somethings that might fail again so best is to update the Service Pack [SP1].

https://support.microsoft.com/en-us/kb/3011055

Regards,

Mekh.

• Edited by Mekh SubbaMicrosoft contingent staff, Moderator Friday, April 24, 2015 2:01 PM spelling

Hey Mekh

Sorry CU5 this didnt help for me, I still cant see Azure database procedures in SSMS,

also now, I can't list table columns so CU5 made it actually worse, any ideas?

What is the link for SP1 download, cause links I have found online are not working

TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
unknown property IsMemoryOptimized (Microsoft.SqlServer.Management.Sdk.Sfc)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------

Hi Ivgoran,

I did a repro for the issue that you are having, I am having SSMS which is on CU6 and it lists the stored procedure.

Microsoft SQL Server Management Studio      12.0.2480.0
Microsoft Analysis Services Client Tools      12.0.2480.0
Microsoft Data Access Components (MDAC)      6.3.9600.17415
Microsoft MSXML      3.0 6.0
Microsoft Internet Explorer      9.11.9600.17728
Microsoft .NET Framework      4.0.30319.34014
Operating System      6.3.9600

Although upgrading SSMS + Client tools connectivity to CU5 should work as we have published in below link as well --

http://azure.microsoft.com/en-us/documentation/articles/sql-database-manage-azure-ssms/)

But as we have released a SP and it has covered many other issues like .bacpac import and DAC publishing, I would request you to update SSMS and client tools connectivity to SP1.

Thanks,

Hitesh

• Edited by chouhanhitesh 22 hours 18 minutes ago

Hi Ivgoran,

I did a repro for the issue that you are having, I am having SSMS which is on CU6 and it lists the stored procedure.

Microsoft SQL Server Management Studio      12.0.2480.0
Microsoft Analysis Services Client Tools      12.0.2480.0
Microsoft Data Access Components (MDAC)      6.3.9600.17415
Microsoft MSXML      3.0 6.0
Microsoft Internet Explorer      9.11.9600.17728
Microsoft .NET Framework      4.0.30319.34014
Operating System      6.3.9600

Although upgrading SSMS + Client tools connectivity to CU5 should work as we have published in below link as well --

http://azure.microsoft.com/en-us/documentation/articles/sql-database-manage-azure-ssms/)

But as we have released a SP and it has covered many other issues like .bacpac import and DAC publishing, I would request you to update SSMS and client tools connectivity to SP1.

Thanks,

Hitesh

• Edited by chouhanhitesh 22 hours 9 minutes ago

Hi Ivgoran,

I did a repro for the issue that you are having, I am having SSMS which is on CU6 and it lists the stored procedure.

Microsoft SQL Server Management Studio      12.0.2480.0
Microsoft Analysis Services Client Tools      12.0.2480.0
Microsoft Data Access Components (MDAC)      6.3.9600.17415
Microsoft MSXML      3.0 6.0
Microsoft Internet Explorer      9.11.9600.17728
Microsoft .NET Framework      4.0.30319.34014
Operating System      6.3.9600

Although upgrading SSMS + Client tools connectivity to CU5 should work as we have published in below link as well --

http://azure.microsoft.com/en-us/documentation/articles/sql-database-manage-azure-ssms/)

But as we have released a SP and it has covered many other issues like .bacpac import and DAC publishing, I would request you to update SSMS and client tools connectivity to SP1.

Thanks,

Hitesh

• Edited by chouhanhitesh Monday, April 27, 2015 8:57 AM

Hi Ivgoran,

I did a repro for the issue that you are having, I am having SSMS which is on CU6 and it lists the stored procedure.

Microsoft SQL Server Management Studio      12.0.2480.0
Microsoft Analysis Services Client Tools      12.0.2480.0
Microsoft Data Access Components (MDAC)      6.3.9600.17415
Microsoft MSXML      3.0 6.0
Microsoft Internet Explorer      9.11.9600.17728
Microsoft .NET Framework      4.0.30319.34014
Operating System      6.3.9600

Although upgrading SSMS + Client tools connectivity to CU5 should work as we have published in below link as well --

http://azure.microsoft.com/en-us/documentation/articles/sql-database-manage-azure-ssms/)

But as we have released a SP and it has covered many other issues like .bacpac import and DAC publishing, I would request you to update SSMS and client tools connectivity to SP1.

Thanks,

Hitesh

• Edited by chouhanhitesh Monday, April 27, 2015 8:57 AM

Hi Ivgoran,

I did a repro for the issue that you are having, I am having SSMS which is on CU6 and it lists the stored procedure.

Microsoft SQL Server Management Studio      12.0.2480.0
Microsoft Analysis Services Client Tools      12.0.2480.0
Microsoft Data Access Components (MDAC)      6.3.9600.17415
Microsoft MSXML      3.0 6.0
Microsoft Internet Explorer      9.11.9600.17728
Microsoft .NET Framework      4.0.30319.34014
Operating System      6.3.9600

Although upgrading SSMS + Client tools connectivity to CU5 should work as we have published in below link as well --

http://azure.microsoft.com/en-us/documentation/articles/sql-database-manage-azure-ssms/)

But as we have released a SP and it has covered many other issues like .bacpac import and DAC publishing, I would request you to update SSMS and client tools connectivity to SP1.

Thanks,

Hitesh

• Edited by chouhanhitesh Monday, April 27, 2015 8:57 AM

Hi Ivgoran,

I did a repro for the issue that you are having, I am having SSMS which is on CU6 and it lists the stored procedure.

Microsoft SQL Server Management Studio      12.0.2480.0
Microsoft Analysis Services Client Tools      12.0.2480.0
Microsoft Data Access Components (MDAC)      6.3.9600.17415
Microsoft MSXML      3.0 6.0
Microsoft Internet Explorer      9.11.9600.17728
Microsoft .NET Framework      4.0.30319.34014
Operating System      6.3.9600

Although upgrading SSMS + Client tools connectivity to CU5 should work as we have published in below link as well --

http://azure.microsoft.com/en-us/documentation/articles/sql-database-manage-azure-ssms/)

But as we have released a SP and it has covered many other issues like .bacpac import and DAC publishing, I would request you to update SSMS and client tools connectivity to SP1.

Thanks,

Hitesh

• Edited by chouhanhitesh Monday, April 27, 2015 8:57 AM

Thanks

but neither CU5 nor CU6 nor CU7 did solve the issue for me

This is really very frustrating, I am regretting I ever upgraded SQL Azure to 13

Plus

What SP are you talking about? http://blogs.technet.com/b/dataplatforminsider/archive/2015/04/17/sql-server-2014-service-pack-1-update.aspx

Hi Ivgoran,

Are you upgrading the client tools connectivity component or not, if not then please upgrade that as well as this is required, if yes and you are still facing the issue, please open a ticket and we will work with you to resolve this.

Thanks,

Hitesh

Hi Ivgoran,

Are you upgrading the client tools connectivity component or not, if not then please upgrade that as well as this is required, if yes and you are still facing the issue, please open a ticket and we will work with you to resolve this.

Thanks,

Hitesh

• Proposed as answer by Mekh SubbaMicrosoft contingent staff, Moderator 22 hours 54 minutes ago

Hi Ivgoran,

Are you upgrading the client tools connectivity component or not, if not then please upgrade that as well as this is required, if yes and you are still facing the issue, please open a ticket and we will work with you to resolve this.

Thanks,

Hitesh

• Proposed as answer by Mekh SubbaMicrosoft contingent staff, Moderator 23 hours 4 minutes ago

Hi Ivgoran,

Are you upgrading the client tools connectivity component or not, if not then please upgrade that as well as this is required, if yes and you are still facing the issue, please open a ticket and we will work with you to resolve this.

Thanks,

Hitesh

• Proposed as answer by Mekh SubbaMicrosoft contingent staff, Moderator Thursday, April 30, 2015 8:12 AM
• Marked as answer by Mekh SubbaMicrosoft contingent staff, Moderator 21 hours 25 minutes ago
• Unmarked as answer by ivgoran 21 hours 23 minutes ago

Hi Ivgoran,

Are you upgrading the client tools connectivity component or not, if not then please upgrade that as well as this is required, if yes and you are still facing the issue, please open a ticket and we will work with you to resolve this.

Thanks,

Hitesh

• Proposed as answer by Mekh SubbaMicrosoft contingent staff, Moderator Thursday, April 30, 2015 8:12 AM
• Marked as answer by Mekh SubbaMicrosoft contingent staff, Moderator 21 hours 35 minutes ago
• Unmarked as answer by ivgoran 21 hours 33 minutes ago

Hi Ivgoran,

Are you upgrading the client tools connectivity component or not, if not then please upgrade that as well as this is required, if yes and you are still facing the issue, please open a ticket and we will work with you to resolve this.

Thanks,

Hitesh

• Proposed as answer by Mekh SubbaMicrosoft contingent staff, Moderator Thursday, April 30, 2015 8:12 AM
• Marked as answer by Mekh SubbaMicrosoft contingent staff, Moderator Friday, May 01, 2015 9:41 AM
• Unmarked as answer by ivgoran Friday, May 01, 2015 9:43 AM

Hi Ivgoran,

Are you upgrading the client tools connectivity component or not, if not then please upgrade that as well as this is required, if yes and you are still facing the issue, please open a ticket and we will work with you to resolve this.

Thanks,

Hitesh

• Proposed as answer by Mekh SubbaMicrosoft contingent staff, Moderator Thursday, April 30, 2015 8:12 AM
• Marked as answer by Mekh SubbaMicrosoft contingent staff, Moderator Friday, May 01, 2015 9:41 AM
• Unmarked as answer by ivgoran Friday, May 01, 2015 9:43 AM

Hi Ivgoran,

Are you upgrading the client tools connectivity component or not, if not then please upgrade that as well as this is required, if yes and you are still facing the issue, please open a ticket and we will work with you to resolve this.

Thanks,

Hitesh

• Proposed as answer by Mekh SubbaMicrosoft contingent staff, Moderator Thursday, April 30, 2015 8:12 AM
• Marked as answer by Mekh SubbaMicrosoft contingent staff, Moderator Friday, May 01, 2015 9:41 AM
• Unmarked as answer by ivgoran Friday, May 01, 2015 9:43 AM

Hi Ivgoran,

Are you upgrading the client tools connectivity component or not, if not then please upgrade that as well as this is required, if yes and you are still facing the issue, please open a ticket and we will work with you to resolve this.

Thanks,

Hitesh

• Proposed as answer by Mekh SubbaMicrosoft contingent staff, Moderator Thursday, April 30, 2015 8:12 AM
• Marked as answer by Mekh SubbaMicrosoft contingent staff, Moderator Friday, May 01, 2015 9:41 AM
• Unmarked as answer by ivgoran Friday, May 01, 2015 9:43 AM

installing the CU caused only not to be able to start SQL Express service I had on my machine

so solution that worked for me was to uninstall everything, reinstall Express SQL I had

and be happy with NOT BEING ABLE to use Azure 13

• Edited by ivgoran 21 hours 15 minutes ago

installing the CU caused only not to be able to start SQL Express service I had on my machine

so solution that worked for me was to uninstall everything, reinstall Express SQL I had

and be happy with NOT BEING ABLE to use Azure 13

• Edited by ivgoran 21 hours 5 minutes ago

installing the CU caused only not to be able to start SQL Express service I had on my machine

so solution that worked for me was to uninstall everything, reinstall Express SQL I had

and be happy with NOT BEING ABLE to use Azure 13

• Edited by ivgoran Friday, May 01, 2015 10:01 AM

installing the CU caused only not to be able to start SQL Express service I had on my machine

so solution that worked for me was to uninstall everything, reinstall Express SQL I had

and be happy with NOT BEING ABLE to use Azure 13

• Edited by ivgoran Friday, May 01, 2015 10:01 AM
• Marked as answer by Mekh SubbaMicrosoft contingent staff, Moderator 23 hours 7 minutes ago

installing the CU caused only not to be able to start SQL Express service I had on my machine

so solution that worked for me was to uninstall everything, reinstall Express SQL I had

and be happy with NOT BEING ABLE to use Azure 13

• Edited by ivgoran Friday, May 01, 2015 10:01 AM
• Marked as answer by Mekh SubbaMicrosoft contingent staff, Moderator 23 hours 16 minutes ago

installing the CU caused only not to be able to start SQL Express service I had on my machine

so solution that worked for me was to uninstall everything, reinstall Express SQL I had

and be happy with NOT BEING ABLE to use Azure 13

• Edited by ivgoran Friday, May 01, 2015 10:01 AM
• Marked as answer by Mekh SubbaMicrosoft contingent staff, Moderator Monday, May 04, 2015 8:00 AM

installing the CU caused only not to be able to start SQL Express service I had on my machine

so solution that worked for me was to uninstall everything, reinstall Express SQL I had

and be happy with NOT BEING ABLE to use Azure 13

• Edited by ivgoran Friday, May 01, 2015 10:01 AM
• Marked as answer by Mekh SubbaMicrosoft contingent staff, Moderator Monday, May 04, 2015 8:00 AM

installing the CU caused only not to be able to start SQL Express service I had on my machine

so solution that worked for me was to uninstall everything, reinstall Express SQL I had

and be happy with NOT BEING ABLE to use Azure 13

• Edited by ivgoran Friday, May 01, 2015 10:01 AM
• Marked as answer by Mekh SubbaMicrosoft contingent staff, Moderator Monday, May 04, 2015 8:00 AM