无法将SQL Azure bacpac导入2016 CTP [英] Cannot import SQL Azure bacpac to 2016 CTP

问题描述

我非常熟悉从Azure SQL V12导出到我的dev框，然后再导入到本地sql(2014)实例的过程.我正在纺一个新的Win10盒子并安装了SQL 2016 CTP.我正在连接到同一Azure实例，并且可以对其进行操作-可以像2014年一样导出.bacpac.

I'm very familiar with the process of exporting from Azure SQL V12 down to my dev box and then importing to my local sql (2014) instance. I'm spinning up a new Win10 box and have installed the SQL 2016 CTP. I'm connecting to that same Azure instance and can operate against it -- and can export a .bacpac just as with 2014.

但是当我尝试导入本地时，我得到了:

But when I try to import to local I'm getting:

Could not import package.
Warning SQL72012: The object [FOO33_Data] exists in the target, but it will not be dropped even though you selected the 'Generate drop statements for objects that are in the target database but that are not in the source' check box.
Warning SQL72012: The object [FOO33_Log] exists in the target, but it will not be dropped even though you selected the 'Generate drop statements for objects that are in the target database but that are not in the source' check box.
Error SQL72014: .Net SqlClient Data Provider: Msg 547, Level 16, State 0, Line 3 The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "FK_dbo.Address_dbo.User_idUser". The conflict occurred in database "FOO33", table "dbo.User", column 'idUser'.
Error SQL72045: Script execution error.  The executed script:
PRINT N'Checking constraint: FK_dbo.Address_dbo.User_idUser [dbo].[Address]';

ALTER TABLE [dbo].[Address] WITH CHECK CHECK CONSTRAINT [FK_dbo.Address_dbo.User_idUser];

推荐答案

由于在MSDN上也有人提出并回答了这个问题，因此我将在这里分享.

Since this question was also asked and answered on MSDN, I will share here. https://social.msdn.microsoft.com/Forums/azure/en-US/0b025206-5ea4-4ecb-b475-c7fabdb6df64/cannot-import-sql-azure-bacpac-to-2016-ctp?forum=ssdsgetstarted

链接答案中的文字:

我怀疑这是哪里出了问题，导出操作是使用数据库实例执行的，而该数据库实例在导出过程中一直在变化.这可能导致导出的表数据不一致，因为与SQL Server的物理备份/还原不同，导出不能保证事务的一致性.相反，它们实际上是通过依次连接到数据库中的每个表并运行select *来执行的.当两个表之间存在外键关系并且读取的表数据不一致时，在将数据写入数据库并且导入代码尝试重新启用外键之后，导入过程中会导致错误.我们建议使用数据库复制机制(将数据库copyDb创建为originalDb的副本)，该机制可确保副本具有事务一致性，然后从不变的数据库副本中导出.

I suspect what's going wrong here is that the export operation was performed using a DB instance that was changing while the export was on-going. This can cause the exported table data to be inconsistent because, unlike SQL Server's physical backup/restore, exports do not guarantee transactional consistency. Instead, they're essentially performed by connecting to each table in the database in turn and running select *. When a foreign key relationship exists between two tables and the read table data is inconsistent, it results in an error during import after the data is written to the database and the import code attempts to re-enable the foreign key. We suggest using the database copy mechanism (create database copyDb as copy of originalDb), which guarantees a copy with transactional consistency, and then exporting from the non-changing database copy.

这篇关于无法将SQL Azure bacpac导入2016 CTP的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！