SqlDatabase export to Bacpac using SqlPackage.exe does not work on fillfactor

I use the following command to execute sqlpackage to export bacpac to local db.

"C: \ Program Files (x86) \ Microsoft SQL Server \ 110 \ DAC \ bin \ sqlpackage.exe" / action: Export / tf: ". \ Dbname_Baseline.bacpac" / SourceConnectionString: "XXXXXXXXXXXX"

I can’t say "The primary key of the element: [dbo]. [PK_Name] has an unsupported FillFactor property and is not supported when used as part of a data packet."

I understand fillfactor is not supported, but is there anything to ignore unsupported properties?

thanks

Mark

+8
export azure-sql-database bacpac fillfactor
source share
2 answers

Pass switch

/p:IgnoreFillFactor ={ True | False } 
+1
source share

I experimented with exporting to bacpac for a small database about 1 GB in size, and you can reconfigure the fillfactor in the database. In SQL Server Manager Studio, just remove and recreate the script for the index, edit the created script to remove the fillfactor specification, run the script, and this will recreate the index with the default factor filling, acceptable for sqlpackage.exe. This should work for both PCs and indexes, it should be fast for small databases and should not have a negative impact on the database.

I understand that this does not answer the question that sqlpackage.exe ignores some errors, but this is probably the best way to fix the problem, since it does it directly in the database.

+1
source share

All Articles