Azure SQL Server 2014 Express VM: Cannot update/patch SQL Server Express - azure

I created an Azure Resource Manager VM using the standard Azure image "SQL Server 2014 SP1 Express on Windows Server 2012 R2".
I immediately ran Windows Update and all patches for the server worked but the Security Update for SQL Server 2014 Service Pack 1 (KB3070446) failed with a error code of 84B30002.
The Azure VM SQL Express version (SELECT ##VERSION) is:
Microsoft SQL Server 2014 - 12.0.4193.9 (X64) Nov 28 2015 03:44:12
Copyright (c) Microsoft Corporation Express Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)
This version is not a documented SQL Server 2014 Express version (as far as I can see here).
I have tried installing CU 5 for SQL Server 2014 Express but that couldn't find a valid version of SQL Server to update.
Do you think it is non-standard version of SQL Server Express that is causing the update to fail? I am stuck.

“Named” instance (SQLEXPRESS) will use dynamic port
"DEFAULT" instance (MSSQLSERVER) will use 1433 as a default one.
If you want to use “Named” instance (SQLEXPRESS) configure the firewall properly or else Change the dynamic port in SQL server configuration.

I raised a ticket with Microsoft and they confirmed that the SQL Express version number caused the problem. Their response was:
the product team has confirmed that the "SQL Server 2014 SP1 Express
on Windows Server 2012 R2" image was wrongly built by an internal
builds (12.0.4193.9).
I am not sure when they will have it fixed. As a workaround I uninstalled SQL Express and re-installed from a public download of SQL Express.
Please NOTE: I had to install the SQL Express as a "DEFAULT" instance (MSSQLSERVER). I tried to install the new SQL Express as a “Named” instance (SQLEXPRESS) instead of the “default” instance (MSSQLSERVER). This didn’t work for me however. I found that I couldn’t contact SQL Server from my other VM that was running my application. So I installed SQL Express as a “default” instance and communication from the other VM started working!

Related

Determine SQL Server components installed

I have been given a laptop running on Windows 10 (this is my first experience of windows 10) and SQL Server 2017 Developer Edition is installed. How can I determine what components are installed with the SQL Server please? I need to know if the Report Builder or Reporting Services tools are setup. If not can they easily be added?
Found that in the SQL Server installation centre there is a component to show all installed components.
https://learn.microsoft.com/en-us/sql/database-engine/install-windows/validate-a-sql-server-installation

SQL Server 2016 Express LocalDB Download Fails

The download link for the SQL Server 2016 Express LocalDB redistributable (sqllocaldb.msi) is broken.
The link I have been using in the past, that one worked fine. Since there is no bootstrapper package available for SQL Server 2016 Express LocalDB in Visual Studio 2015, I created my own using this link. It used to work (most of the time). Now it's completely broken. (See this on msdn forum)
Also the download link in the topic "SQL Server 2016 Express LocalDB" is also broken.
Does anyone know how to fix this? I have also posted this on Microsoft Connect - SQL Server.

The data source provider for data sources of type 'ADOMD.NET' is not registered

I am working on sharepoint 2013 ,while working on Performance Point Service when i amd connecting to a new Analysis source in Dashboard Designer ,it is not loading databases.
I have googled the problem and found the in my EventLogs it appears
"The data source provider for data sources of type 'ADOMD.NET' is not registered. Please contact an administrator.PerformancePoint Services error code 10115."
I downloaded and installed latest version of ADOMD.NET but it didnt worked.Please Help
If you are using SQL Server 2012 or newer, and SharePoint Server 2013, it will try to load the SQL Server 2008 version of the ADMD.NET dll.
Try to install the SQL Server 2008 R2 ADMD.NET component from here: http://www.microsoft.com/en-us/download/details.aspx?id=16978 and restart IIS.

Unable to import SQL Azure V12 BACPAC: "type Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider is not valid"

I am trying to import the exported BACPAC from an SQL Azure (v12) database into a local SQL Server 2012 instance, but I keep getting the error below. I have tried installing the DAC and SSDT updates linked from this blog post, but it's not helping.
How can I fix this?
TITLE: Microsoft SQL Server Management Studio
------------------------------
Count not load schema model from package. (Microsoft.SqlServer.Dac)
------------------------------
ADDITIONAL INFORMATION:
Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database platform service. (Microsoft.Data.Tools.Schema.Sql)
------------------------------
BUTTONS:
OK
------------------------------
Updated: The new SQL Server Management Studio Preview is the best way to Import to Azure SQL DB. It has support for all the latest Azure SQL DB features and validations. In addition it has a standalone web installer that is automatically updated each month as new features become available. Given comments below mentioning the difficulty of installing a CU update, this would be a simpler & quicker solution to the problem.
Original Answer:
If you are using SQL Server Management Studio to perform the Import, you must have SSMS 2014 CU5 or CU6 installed. Information on installing CU6 is available here. The error shown in your question indicates you're using an older version of SSMS.
**Update: **
In response to Martin's answer below, I'd like to clarify 2 things.
SSMS for SQL Server 2014 is the only version of SSMS with full support of the new Azure SQL DB v12 features, notably Import/Export against this target. This is because v12 has (almost) feature parity with SQL Server 2014 and older versions of the tooling do not have support for this. Note that SSMS 2014 is fully backwards compatible with SQL Server 2005 and up.
There was a separate, temporary issue that caused problems with databases upgraded Azure SQL DB v12. This has been resolved and the correct place to find information about solving this are in section C3 of the Plan and Prepare to Upgrade page. In summary if you've exported a bacpac that is failing to import due to this issue you can download the latest DacFramework.msi from here to fix this issue in SSMS.
Full disclosure: I work on the SQL Server tools team.
To fix import error with [sys].[script_deployment_databases] from exported V12 Database you have to install:
CU13
Microsoft SQL Server Data-Tier Application Framework (February 2015) (you must install BOTH the x64 and x86 versions).
EDIT: CU13 is not necessary, just try second link first!
Install the following and it will work!
1) Have you installed Cumulative Update 5 for SQL Server Management Studio 2014. http://support2.microsoft.com/kb/3011055
2) Microsoft SQL Server Data-Tier Application Framework (February 2015) (you must install BOTH the x64 and x86 versions). http://www.microsoft.com/en-us/download/details.aspx?id=45886
I had the same problem with my dataabse backup from SQL Azure (v12).
I've installed Microsoft® SQL Server® Data-Tier Application Framework (February 2015) (in order to work correctly you will need install BOTH the x64 and x86 versions).
First I've installed x64 version and tried to restore the DB - but it didn't work. After that I've installed x86 version and I could successfully restore the database.
My SQL Server version: Microsoft SQL Server 2014 - 12.0.2269.0 (X64). OS: Windows 10 x64 build 10240.
Tnanks.
BacPac restore from Azure DB fails after installing latest SQL Server Management Studio 2016 Preview. Solution was to set "Contained Database Authentication" = 1 for my local SQL DB instance. Read about solution here or run this script on your local instance:
USE master
GO
RECONFIGURE
GO
sp_configure 'CONTAINED DATABASE AUTHENTICATION', 1
I was using wrong SqlPackage.exe path.
Does not work:
C:\Program Files (x86)\Microsoft SQL Server\110\DAC\bin\SqlPackage.exe
Works:
C:\Program Files (x86)\Microsoft SQL Server\130\DAC\bin\SqlPackage.exe
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\SQLDB\DAC\130\SqlPackage.exe
I'm having the same issue.
Installing Cumulative update package 6 as suggested here helps to avoid the first bug but just to get stuck in the next one.
Related to this topic:
SQL Azure import of bacpac does not work after upgrade to v12
it's a bug Microsoft has no fix or workaround yet.
Edit: SQL Management Studio 2014 is required to restore (2012 doesn't work)
If there's one, I think the thread will be updated.
Edit: In the above mentioned link you now can find a workaround: You need to create a copy of your V12 database. This copy can be exported and reimported on your local sql server 2014.
Just updating the tools doesn't help.
I'm using version 11.0.2100.60 and had the same issue. Installed Microsoft® SQL Server® Data-Tier Application Framework (February 2015). All worked fine after that.

SQL Server 2012 "SQL Browser" Service

As a preface, I have done some checking around on this issue but found nothing that solves my question. This question was the closest I found but the answer did not resolve my issue.
Information about configuration: My local machine is Windows 7 with Visual Studio 2012 Update 3 and SSDT-BI installed. On the server machine I have SQL Server 2012 Developer Edition installed on Windows Server 2012 Standard. The data is coming from a third party database installed on a CentOS5 server.
I am trying to deploy a cube to my Analysis Services server, but I am getting the following error: "A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running."
I have checked and the SQL Browser service is running both on my local machine and the server machine. As well, rather than connecting via < Server Name >\< Instance Name > I have tried connecting with IPAddress:Port.
I'm not sure if this is relevant, but in case it is: the database I am using to define the cube I'm trying to deploy is on a different server and has different authentication than my SQL Server 2012 Instance. Moving the data to the SQL Server is not an option.
To FrankPl: just to chime in, you answered my question a few hours ago which is essentially the same problem: VS2012 Pro with SSDT-BI installed, also Update-3 and the Aug.2013 update to AS. We're unable to connect and/or open a project.

Resources