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

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Conflicting instructio...
Microsoft Dynamics AX (Archived)

Conflicting instructions about importing a .BACPAC file - can 'Import Data-tier application..' be used for .BACPAC files?

(0) ShareShare
ReportReport
Posted on by DD-19021315-0 230

Searching for "restore bacpac to sql server 2016"  brings up the result https://docs.microsoft.com/en-us/sql/relational-databases/data-tier-applications/import-a-bacpac-file-to-create-a-new-user-database

This says to use the "'Import Data-tier application...' option after right-clicking Database in SSMS. However, this will only accept .DACPAC files, not .BACPAC (even after renaming the extension).

Is this, in fact, usable, or are the instructions at the page given incorrect and only the command line tool works> (As at https://docs.microsoft.com/en-us/dynamics365/operations/dev-itpro/database/copy-database-from-azure-sql-to-sql-server)

Can the 'Export Data-tier application..." option be used the export the AxDB to a .DACPAC file and avoid using the command line version?

Thnaks

*This post is locked for comments

I have the same question (0)
  • DD-19021315-0 Profile Picture
    DD-19021315-0 230 on at
    RE: Conflicting instructions about importing a .BACPAC file - can 'Import Data-tier application..' be used for .BACPAC files?

    I must have selected the wrong option in SSMS 2016. I tried it using SSMS 2017, which appeared to be working until it got OutOfMemory errors. I'll just have to use the command line.

  • Tariq Bell MSFTE Profile Picture
    Tariq Bell MSFTE 30 on at
    RE: Conflicting instructions about importing a .BACPAC file - can 'Import Data-tier application..' be used for .BACPAC files?

    For Dynamics 365 for Operations we're saying to use sqlpackage from the command line because the SSMS UI alternative has a 32 bit process memory limit - basically you hit the 2gb memory limit when exporting larger DBs. SQLPackage (despite the fact that it's under program files (x86)), doesn't have the 32 bit limit.

    The bacpac/dacpac piece - the "import data tier application" option only allows selection of a bacpac. The "deploy data tier application" only accepts dacpac. Basically dacpac is about moving schema around - Devs use it when deploying their applications as a way of managing the schema changes, but bacpac is for moving schema and data. There's a better explanation of the difference here: docs.microsoft.com/.../data-tier-applications

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

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

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

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Community Member Profile Picture

Community Member 2

#1
Guy Terry Profile Picture

Guy Terry 2 Moderator

#1
Martin Dráb Profile Picture

Martin Dráb 2 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans