export copy reminder (#34818)

Author: dzsquared

docs/tools/sqlpackage/sqlpackage-export.md

@@ -4,7 +4,7 @@ description: Learn how to automate database development tasks with SqlPackage Ex
 author: dzsquared
 ms.author: drskwier
 ms.reviewer: maghan
-ms.date: 9/29/2022
+ms.date: 07/28/2025
 ms.service: sql
 ms.subservice: tools-other
 ms.topic: conceptual
@@ -13,7 +13,7 @@ ms.collection:
 ---
 
 # SqlPackage Export parameters and properties
-The SqlPackage Export action exports a connected database to a BACPAC file (.bacpac). By default, data for all tables will be included in the .bacpac file. Optionally, you can specify only a subset of tables for which to export data. The Export action is part of the [database portability](sqlpackage.md#portability) functionality of SqlPackage.
+The SqlPackage Export action exports a connected database to a BACPAC file (.bacpac). By default, data for all tables will be included in the .bacpac file. Optionally, you can specify only a subset of tables for which to export data. The Export action is part of the [database portability](sqlpackage.md#portability) functionality of SqlPackage. 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](/azure/azure-sql/database/database-copy) of your database.
 
 [!INCLUDE [entra-id](../../includes/entra-id-hard-coded.md)]
 

docs/tools/sqlpackage/troubleshooting-issues-and-performance-with-sqlpackage.md

@@ -151,6 +151,8 @@ For imports that contain large tables or tables with many indexes, the use of `/
 
 ## Export action tips
 
+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](/azure/azure-sql/database/database-copy) of your database. Receiving errors about foreign key constraints during an import can indicate that the export was not transactionally consistent due to inserted or updated records during the export process.
+
 A common cause of performance degradation during export is unresolved object references, which causes SqlPackage to attempt to resolve the object multiple times. For example, a view is defined that references a table and the table no longer exists in the database. If unresolved references appear in the export log, consider correcting the schema of the database to improve the export performance.
 
 In scenarios where the OS disk space is limited and runs out during the export, the use of `/p:TempDirectoryForTableData` allows the data for export to be buffered on an alternative disk. The space required for this action might be large and is relative to the full size of the database. That and other properties are available to tune the [SqlPackage Export](sqlpackage-export.md) operation.