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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

SQL import to tier1 fails

(0) ShareShare
ReportReport
Posted on by 5

After importing the db from F&O tier2 to tier1 vm with sql package for about 10 minutes, I'm getting *** Error importing database:Could not import package.
 Warning SQL72035: [dbo].[CUSTINVOICEJOUR] is under change data capture control, but those settings will not be transferred [...] from several tables

Then the import fails. Tried different things to resolve with no success. Has anyone been able to resolve this?

I have the same question (0)
  • Mohit Rampal Profile Picture
    12,565 Moderator on at

    Hi Lauri, I haven't faced this issue but did you tried disabling change data capture for CustInvoiceJour table or even at database level and exporting bacpac?

    learn.microsoft.com/.../enable-and-disable-change-data-capture-sql-server

  • Charlotte X Profile Picture
    Microsoft Employee on at

    Hi Lauri,

    I haven't tried this, but I found an old thread that mentions the steps to import into Tier 1 environment.

    (+) Import Azure SQL DB backup to Tier 1 environment - Dynamics 365 Finance Forum Community Forum

  • Komi Siabi Profile Picture
    13,190 Most Valuable Professional on at

    Hi Lauri,

    Could please share the script you used importing the bacpac database?

  • Lauri N Profile Picture
    5 on at

    Yes, .\SqlPackage.exe /a:import /sf:C:\Temp\backup.bacpac /tsn:localhost /tdn:AxDB_NEW /p:CommandTimeout=1200 /TargetTrustServerCertificate:True

  • Suggested answer
    Komi Siabi Profile Picture
    13,190 Most Valuable Professional on at

    Hello Lauri,

    The import sometimes might not really work as expected at a go. I have also encountered similar errors. What I do, and propose is, rename the AxDB and re-import once again.

    Have you tried it already? If not, do and let us know.

  • Lauri N Profile Picture
    5 on at

    >> Hi Lauri, I haven't faced this issue but did you tried disabling change data capture for CustInvoiceJour table or even at database level and exporting bacpac?

    We discussed about this with team, would it be too risky to take it off since the source environment is the UAT environment?

  • Suggested answer
    Mohit Rampal Profile Picture
    12,565 Moderator on at

    Since, it's UAT environment, you can disable it during off peak hours (Dark hours), export bacpac and enable it again.

  • Lauri N Profile Picture
    5 on at

    Renaming the target database to just "NEW" resolved this issue. Thanks

  • Komi Siabi Profile Picture
    13,190 Most Valuable Professional on at

    Great. Glad you got it resolved.

    I believe, you would have to rename the db NEW back to AxDB on the dev.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

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

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 529 Super User 2026 Season 1

#2
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 470

#3
Adis Profile Picture

Adis 270 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans