I have Windows 10 Enterprise Version: 20H2, Experience: Windows Feature Experience Pack 120.2212.4170.0. This upgrade happened last week. I had Oracle 19c server and client installed in my system with a database configured which was working fine before the Windows upgrade. I had all registry entries and the Oracle Windows services were visible under services.msc. I have an application installed which was configured using this same database. Suddenly I am seeing that the Oracle services are not showing under Windows Services, I don't see any registry entries which were there. Please can anyone help if similar issue has been observed and resolved. thanks!
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.
I am looking to install this on a 64 bit system in order to test SQL queries against an ODBC source. The current links are Microsoft are too new. Does anyone know where I can download it from?
SQLCMD should come with Management Studio http://www.microsoft.com/en-us/download/details.aspx?id=7593 However there's no reason why you couldn't use a newer version of SQLCMD to connect to an older database.
For SQL Server 2008 R2, you want to download the files from what is called the Microsoft® SQL Server® 2008 R2 Feature Pack. https://www.microsoft.com/en-us/download/details.aspx?id=16978
From there, you are going to need 2 programs
"Microsoft® SQL Server® 2008 R2 Native Client" X64 Package (sqlncli.msi) and "Microsoft® SQL Server® 2008 R2 Command Line Utilities" X64 Package (SqlCmdLnUtils.msi) in either 32 bit or 64 bit form depending on where you are installing it. Most servers are 64 bit so if doubt, choose that version first.
Install the native client first and command line utilities second.
i am new to the oracle. ,My project is .net web application which is connected to the oracle database(oracle 11g) when i run my solution in local environment, i get the error in the below line saying that "Could not create connection from Driver".
return factory.ConnectionProvider.GetConnection();
but this project is working fine in windows XP and I am using windows 7 with oracle 11g installed in my system where i am facing the problem.please can any one give solution.
I understand from the team that this project is designed with oracle 9.2 in mind. how do i make it work in oracle 11g which i have it currently.
I would advise you to use Oracle's Managed Data Provider for .NET. All your problems with local Oracle installations will go away immediately. Since it's a 100% managed driver, you won't need to install Oracle's client on your machine before connecting to it with .NET programs.
When install SQL Server 2000 (Evaluation copy) on Windows 7 32 bit Home Premium desktop computer,
system gives the following error and Installation not successful:
InstallShield Engine has stopped
working A problem caused the program
to stop working correctly. Windows
will close the program and notify you
if a solution is available.
Sql server 2000 is not supported on Windows 7. You might be able to get it installed but you would have problems.
According to this blog posting you even need SP3 of Sql Server 2005 for it to work on Win7.
http://blogs.msdn.com/sqlreleaseservices/archive/2009/10/23/sql-server-on-windows-7-and-windows-server-2008-r2.aspx