SQL Azure的V12 BACPAC导入错误:"内部目标平台类型SqlAzureV12DatabaseSchemaProvider不支持架构文件版本'3.3'" [英] SQL Azure V12 BACPAC import error: "The internal target platform type SqlAzureV12DatabaseSchemaProvider does not support schema file version '3.3'"

查看:1328
本文介绍了SQL Azure的V12 BACPAC导入错误:"内部目标平台类型SqlAzureV12DatabaseSchemaProvider不支持架构文件版本'3.3'"的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

直到非常几天前我能导​​入从Azure中的V12 BACPAC到我的本地服务器与SQL Server 2014 SP1 CU6(12.0.4449.0)。

Until a very few days ago I was able to import a V12 BACPAC from Azure to my local server with SQL Server 2014 SP1 CU6 (12.0.4449.0).

但现在,当我尝试导入BACPAC,我的SQL Server Management Studio中说,2014年:

But now, when I try to import the BACPAC, my SQL Server Management Studio 2014 says:

内部错误内部目标平台类型SqlAzureV12DatabaseSchemaProvider不支持架构文件版本'3.3'(文件:D:\\ MyDB.bacpac)。(Microsoft.Data.Tools.Schema.Sql)

"Internal Error. The internal target platform type SqlAzureV12DatabaseSchemaProvider does not support schema file version '3.3'. (File: D:\MyDB.bacpac) (Microsoft.Data.Tools.Schema.Sql)"

我想我与所有最新的更新(版本12.0.4449.0),但我仍然得到这个错误最新的SQL Server 2014年SP1版本。

I think I've the latest SQL Server 2014 SP1 version with all the latest updates (build 12.0.4449.0) but still I get this error.

请帮帮忙!

感谢

推荐答案

修正::要解决此问题,使用的最新SSMS preVIEW 将安装最最新DacFx版本。这种理解如何处理最新的功能,尤其是数据库范围配置选项。一旦安装了可以在里面SSMS导入或使用SqlPackage从C:\\ Program Files文件(x86)的\\ Microsoft SQL Server的\\ 130 \\ DAC \\ bin中。位置,如果你preFER命令行工具

Fix: To resolve, use the latest SSMS Preview which installs the most up to date DacFx version. This understands how to process the latest features, notably Database Scoped Configuration Options. Once this is installed you can Import inside SSMS or using SqlPackage from the "C:\Program Files (x86)\Microsoft SQL Server\130\DAC\bin" location if you prefer command line tools.

另外,关于Az​​ure的DB执行下面的命令来设置MAXDOP值返回到默认值,因为它出现的问题是,这已被更改为1,未来出口现在应该生成可由2014年的客户端工具可以理解bacpacs,假设没有其他新的Azure功能已被添加到数据库。

Alternatively, execute the following command on the Azure DB to set MaxDop value back to default since it appears the issue is that this has been changed to 1. Future exports should now produce bacpacs that can be understood by the 2014 client tools, assuming no other new Azure features have been added to the DB.

ALTER DATABASE SCOPED CONFIGURATION SET MAXDOP = 0

根源/为什么会发生这种情况:的根本原因是,你的数据库有1个或多个数据库范围的配置选项非默认值。由于这些只增加非常最近,老版本的工具并不了解如何部署他们等等DacFx块。这些都是与高某架构版本的唯一属性/对象。基本上你看到的任何时间,如不支持模式文件版本'3.3'的错误就意味着你需要升级。一个可能的原因是,如果数据库是从AzureV1迁移 - > AzureV12,从它的默认值0。

Root cause / why does this happen: The root cause is that your database have non-default values for 1 or more Database Scoped Configuration options. As these were only added very recently, older versions of the tools do not understand how to deploy them and so DacFx blocks. These are the only properties/objects with that high a schema version. Basically any time you see an error like "does not support schema file version '3.3'" it means you need to upgrade. One possible cause is if the database was migrated from AzureV1 -> AzureV12, which sets the MaxDop option to 1 from its default of 0.

注:我们强烈建议您使用最新的SSMS并保持它通过内置的更新通知的日期,如果你使用Azure的工作。这将确保你避免陷入像这样的问题。一般来说,如果你只使用SQL Server 2014的表面积,你应该能够使用重新导入时,旧的工具,但在Azure中的SQL数据库的情况下这样的最新进展的大量多会突然出现,更经常在那里的新工具需要以达到预期效果。

Notes: It's strongly recommended that you use the latest SSMS and keep it up to date via the built-in update notifications if you're working with Azure. it will ensure that you avoid running into issues like this one. Generally if you only use the SQL Server 2014 surface area you should be able to use older tools when re-importing, but with the huge number of recent advancements in Azure SQL DB cases like this will crop up more and more often where the new tools are required in order to perform as expected.

有关参考,我包括数据库范围配置选项和低于其默认值。如果这些属性都在DB非默认时,导出架构版本被撞到,这样旧的工具不破。

For reference, I’m including the Database Scoped Configuration options and their default values below. If any of these properties are non-default on the DB when exporting the schema version gets bumped so that old tools do not break.

<!-- Database Scoped Configurations-->
<Property Name="MaxDop" Type="System.Int32" DefaultValue="0" />
<Property Name="MaxDopForSecondary" Type="System.Int32?" DefaultValue="null"/>
<Property Name="LegacyCardinalityEstimation" Type="System.Boolean" DefaultValue="false" />
<Property Name="LegacyCardinalityEstimationForSecondary" Type="System.Boolean?" DefaultValue="null" />
<Property Name="ParameterSniffing" Type="System.Boolean" DefaultValue="true" />
<Property Name="ParameterSniffingForSecondary" Type="System.Boolean?" DefaultValue="null" />
<Property Name="QueryOptimizerHotfixes" Type="System.Boolean" DefaultValue="false" />
<Property Name="QueryOptimizerHotfixesForSecondary" Type="System.Boolean?" DefaultValue="null" />

这篇关于SQL Azure的V12 BACPAC导入错误:&QUOT;内部目标平台类型SqlAzureV12DatabaseSchemaProvider不支持架构文件版本'3.3'&QUOT;的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆