Skip to main content

Notifications

Announcements

Check out the New Agent Creator Community
Announcing new navigation menus and the Engage with the Community forum!
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,231

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.

  • Suggested answer
    Gokul.S Profile Picture
    Gokul.S 2 on at
    SQLPackage Import Error
    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.
  • Andrew Friebel Profile Picture
    Andrew Friebel 12 on at
    SQLPackage Import Error
    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.
  • Jan M. Profile Picture
    Jan M. 3,231 on at
    SQLPackage Import Error
    Even with the most recent patch SQLServer2019-KB5027702-x64 the feature is not there.
    Will go with the script.
     
    Thanks a lot Martin.
  • Community member Profile Picture
    Community member 2 on at
    SQLPackage Import Error
    Did you manage to resolve?
  • Verified answer
    Martin Dráb Profile Picture
    Martin Dráb 234,035 Most Valuable Professional on at
    SQLPackage Import Error
    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).

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

News and Announcements

Check out the New Agent Creator Community
Announcing new navigation menus and the Engage with the Community forum!

Quick Links

Jainam Kothari – Community Spotlight

We are honored to recognize Jainam Kothari as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard >

Last month Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans