web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / SQLPackage Import Error
Finance | Project Operations, Human Resources, ...
Answered

SQLPackage Import Error

(1) ShareShare
ReportReport
Posted on by Jan M. 3,262

Hi

After 1h the import of the .bacpac fails with the error: Error SQL72014: Core Microsoft SqlClient Data Provider: Msg 155, Level 15, State 1, Line 3 'AUTO_DROP' is not a recognized CREATE STATISTICS option.

New Test VM with SQL Server 2019: 15.0.4316.3

sqlpackage.exe: 162.0.52.1

May the sqlpackage is to new but I didn't find the one who fits exactly.

Thanks for your help.

I have the same question (0)
  • Verified answer
    Martin Dráb Profile Picture
    Martin Dráb 237,801 Most Valuable Professional on at
    This is a known issues caused by a new feature that isn't available in the version of SQL Server on T1 boxes.
     
    If you have access to Insider Program Yammer forum, you can find it discussed in detail there (https://www.yammer.com/dynamicsaxfeedbackprograms/#/Threads/show?threadId=2382104258371584).
     
    In short, the most common recommendation is unzipping the bacpac and removing references to AutoDrop from model.xml. You can even find some scripts to help with it (https://github.com/d365collaborative/d365fo.tools/issues/747).
  • Community member Profile Picture
    Community member 2 on at
    Did you manage to resolve?
  • Jan M. Profile Picture
    Jan M. 3,262 on at
    Even with the most recent patch SQLServer2019-KB5027702-x64 the feature is not there.
    Will go with the script.
     
    Thanks a lot Martin.
  • Andrew Friebel Profile Picture
    Andrew Friebel 12 on at
    You can also upgrade Tier1 boxes SQL to SQL2022.
     
    Check to ensure you have the developer edition using SELECT @@version in SSMS.
     
    If you do, then you can upgrade it to SQL 2022 developer version as well.
     
     
    Ensure you download the developer version.  When you run the setup, you need to ensure your installation is an upgrade from a previous version, and ensure you you stipulate the developer edition through the install process.  Once you have updated to SQL2022 on the Tier1, then you should be right with importing the bacpac files.
     
    It's my understanding that SQL2019 is still part of the default build on a Tier1 at the time of writing this post.
  • Suggested answer
    Gokul.S Profile Picture
    Gokul.S 2 on at
    Hi,

    I had the same issue AUTO_DROP' is not a recognized CREATE STATISTICS option.,
    its very simple,

    https://learn.microsoft.com/en-us/sql/tools/sqlpackage-download#get-sqlpackage-net-core-for-windows
    --Installation, zip download - download first zip file.

    continue the same process.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 660 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 549 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 307 User Group Leader

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans