自动SQL Azure的出口DB失败 - 不支持MS SQL Azure的V12数据库索引的文档类型的.xml [英] Automated Azure SQL DB export fails - indexing for document type .xml is not supported on MS Azure SQL DB v12

问题描述

我使用Azure的SQL数据库的自动导出功能。一切工作就像一个魅力，但最近它开始失败的：

  在2015年8月2日上午4点11分22秒XXX：

SQL自动导出失败XXX。临时数据库副本被做了，但是这个副本不能导出到.bacpac文件。

我已经签导入/导出历史记录我的Azure的SQL Server，看到以下错误信息：

  

业务操作过程中遇到的错误。不支持微软的Azure SQL数据库索引V12文档类型的.xml。

我不知道它是什么。也许它的东西与我使用FTS功能联系在一起，但自从我上一次成功的自动出口，我没有这样做对我的数据库，所以我想这一定是有天青问题。

1. 请你知道如何解决这一问题？


2. 请你知道，如果它影响默认湛蓝的SQL数据库服务进行备份？

解决方案

披露：我在负责导入/导出SQL Server团队工作。一种在自动出口这个问题修复将在未来增加，但立即解决办法是使用SqlPackage.exe本地出口。解决的办法是设置VerifyFullTextDocumentTypesSupported标志是假的在萨蒂亚的回答提到。

具体步骤使用SqlPackage.exe：

1. 安装 7月最新发布DacFramework.msi ，或安装最好有支持的最新SSMS preVIEW 最新的SQL Azure的DB特性。全文搜索支持，该配置选项是今年新增的，因此需要更新SqlPackage.exe。您正在使用导出的版本已经过时，因此不知道全文搜索的支持。


2. 运行以下命令，使用SqlPackage.exe出口。

有关120版本（这是七月RTM更新）：

 C：\\ Program Files文件（x86）的\\ Microsoft SQL Server的\\ 120 \\ DAC \\ BIN \\ SqlPackage.exe/ A：出口/ SSN：（的LocalDB）\\ ProjectsV12 / SDN ：MYDB /tf:my.bacpac / p：VerifyFullTextDocumentTypesSupported = FALSE
 

有关130版本（由SSMS preVIEW版本安装）：

 C：\\ Program Files文件（x86）的\\ Microsoft SQL Server的\\ 130 \\ DAC \\ BIN \\ SqlPackage.exe/ A：出口/ SSN：（的LocalDB）\\ ProjectsV12 / SDN ：MYDB /tf:my.bacpac / p：VerifyFullTextDocumentTypesSupported = FALSE
 

最后，要回答你的问题＃2这不会影响备份或时间点恢复（PITR）。这是一个配置问题导入/导出服务，问题是局部此功能。

I'm using Azure SQL DB automated export feature. Everything worked like a charm, but recently it started failing:

Automated SQL Export failed for XXX:XXX at 8/2/2015 4:11:22 AM. The temporary database copy was made, but this copy could not be exported to the .bacpac file.

I've checked "Import/Export History" of my Azure SQL Server and saw following error details:

Error encountered during the service operation. Indexing for document type .xml is not supported on Microsoft Azure SQL Database v12.

I have no idea what it is. Probably it's something linked with FTS feature that I'm using, but I've done nothing to my database since my last successful automated exports, so I guess this must be some Azure issue.

1. Do you know how to fix this?
2. Do you know if it affects backups made by default by Azure SQL DB service?

解决方案

Disclosure: I work on the SQL Server team responsible for Import/Export. A fix for this issue during automated export will be added in the future, but an immediate workaround is to use SqlPackage.exe to export locally. The solution is to set the VerifyFullTextDocumentTypesSupported flag to be false as mentioned in Satya's answer.

Exact steps to use SqlPackage.exe:

1. Install the latest July DacFramework.msi release, or ideally install the latest SSMS Preview which has support for the most recent Azure SQL DB features. Support for Full Text Search and this config option was added this year, hence the need to update SqlPackage.exe. The version you were using to Export was out of date and hence did not know about Full Text Search support.
2. Run the following command to export using SqlPackage.exe.

For version 120 (this is the July RTM update):

"C:\Program Files (x86)\Microsoft SQL Server\120\DAC\bin\SqlPackage.exe" /a:export /ssn:(localdb)\ProjectsV12 /sdn:myDB /tf:my.bacpac /p:VerifyFullTextDocumentTypesSupported=false

For version 130 (Installed by SSMS Preview release):

"C:\Program Files (x86)\Microsoft SQL Server\130\DAC\bin\SqlPackage.exe" /a:export /ssn:(localdb)\ProjectsV12 /sdn:myDB /tf:my.bacpac /p:VerifyFullTextDocumentTypesSupported=false

Finally, to answer your question #2 this will not affect backups or Point in Time Restore (PITR). It is a configuration issue with the Import/Export service and the issue is localized to this feature.

这篇关于自动SQL Azure的出口DB失败 - 不支持MS SQL Azure的V12数据库索引的文档类型的.xml的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！