Skip to main content

Notifications

Announcements

No record found.

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?

  • Komi Siabi Profile Picture
    Komi Siabi 12,759 Most Valuable Professional on at
    RE: SQL import to tier1 fails

    Great. Glad you got it resolved.

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

  • Lauri N Profile Picture
    Lauri N 5 on at
    RE: SQL import to tier1 fails

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

  • Suggested answer
    Mohit Rampal Profile Picture
    Mohit Rampal 12,554 Super User 2024 Season 1 on at
    RE: SQL import to tier1 fails

    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
    Lauri N 5 on at
    RE: SQL import to tier1 fails

    >> 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
    Komi Siabi Profile Picture
    Komi Siabi 12,759 Most Valuable Professional on at
    RE: SQL import to tier1 fails

    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
    Lauri N 5 on at
    RE: SQL import to tier1 fails

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

  • Komi Siabi Profile Picture
    Komi Siabi 12,759 Most Valuable Professional on at
    RE: SQL import to tier1 fails

    Hi Lauri,

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

  • Charlotte X Profile Picture
    Charlotte X on at
    RE: SQL import to tier1 fails

    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

  • Mohit Rampal Profile Picture
    Mohit Rampal 12,554 Super User 2024 Season 1 on at
    RE: SQL import to tier1 fails

    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

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

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Congratulations to the January Top 10 leaders!

Check out the January community rock stars...

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,162 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 230,962 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans