Question Details

No question body available.

Tags

sql-server azure database-backups

Answers (1)

Accepted Answer Available
Accepted Answer
March 8, 2026 Score: 5 Rep: 10,834 Quality: Expert Completeness: 100%

From the "Export to a BACPAC File" documentation:

For an export to be transactionally consistent, you must ensure either that no write activity is occurring during the export, or that you're exporting from a transactionally consistent copy of your database.

Is it possible that the .BACPAK was created from an active database and changes were applied to the source database between the time the TmXOrder table data was extracted and TmXLoanApplication table data was extracted? This would explain the error you are getting.

I'm not the Azure expert here, but this answer suggests that one solution may be to:

  1. Take a backup of your database or identify a recent existing backup. (Backups should be transactionally consistent.)
  2. Restore that backup to a different database name, such as "XYZCopy").
  3. Create a .BACPAC file from the "XYZCopy" database.
  4. Drop the "XYZCopy" database.

If this were a regular SQL server, I would suggest creating a database snapshot and exporting from that, but I do not know if Azure has an equivalent capability.