User Profile
ToniPohl
MVP
Joined Feb 11, 2017
User Widgets
Recent Discussions
Re: BACPAC: Could not import package. SQL72012
Hi Fredrik, yes! It turned out that when I imported the same database into another SQL Azure Server, I received the following error: Could not import package. Error SQL72014: .Net SqlClient Data Provider: Msg 468, Level 16, State 9, Procedure vwSomeView, Line 3 Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the UNION operation. Error SQL72045: Script execution error. The executed script: CREATE VIEW [dbo].[vwSomeView] ... So, this lead me to the solution. Obviously, in my database, I added some new columns and that was done in with a different collation. That caused my errors. To make it short, my solution had 2 parts: 1. https://www.sqlservercentral.com/Forums/PrintTopic1886371.aspx 2. I needed to convert all columns to the same collation, similar as here: ALTER TABLE MyTable ALTER COLUMN [MyColumn1] varchar(MAX) COLLATE Latin1_General_CI_AS NULL Since this would mean a lot of effort I found a Stored Procedure script that runs through all tables and generates that ALTER script from https://stackoverflow.com/questions/18122773/change-collations-of-all-columns-of-all-tables-in-sql-server After These two steps, I regenerated the BACPAC and I was able to Import that database. I hope I find some time to publish that in my blog in the next days to make a detailled description about my scenario. Hope that helps?! br, ToniBACPAC: Could not import package. SQL72012
Hi SQL-guys, I'm running into this error during the last days and could not find a solution: I am trying to import a database .BACPAC file from SQL Azure into my local SQL Server. When doing so, I get this error on my local machine: Could not import package. Warning SQL72012: The object [mydb_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 [mydb_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. I found this post (among with others...): https://www.sqlservercentral.com/Forums/PrintTopic1886371.aspx sp_configure 'contained database authentication', 1; GO RECONFIGURE; GO Interestingly, this reconfiguration worked once some days ago with another database. But now, I'm stuck, it doesn't work for me. [ I even installed the latest version of SQL Server Management Studio (SSMS) 17.2 from https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms but without success. ] Tips anyone? thx! Toni
