https://github.com/MicrosoftDocs/sql-docs/issues/8394

dzsquared · dzsquared · commit 12f639067716 · 2022-12-19T16:05:05.000-08:00
diff --git a/docs/tools/sqlpackage/sqlpackage-export.md b/docs/tools/sqlpackage/sqlpackage-export.md
@@ -22,6 +22,9 @@ The SqlPackage.exe Export action exports a connected database to a BACPAC file (
 SqlPackage /Action:Export {parameters} {properties}
 ```
 
+> [!NOTE]
+> SqlPackage export performs best for databases under 200GB. For larger databases, you may want to optimize the operation using properties available in this article and tips in [Troubleshooting with SqlPackage](./troubleshooting-issues-and-performance-with-sqlpackage.md).
+
 ### Examples
 
 ```bash
diff --git a/docs/tools/sqlpackage/sqlpackage-import.md b/docs/tools/sqlpackage/sqlpackage-import.md
@@ -14,6 +14,10 @@ ms.date: 9/29/2022
 # SqlPackage Import parameters and properties
 The SqlPackage.exe Import action imports the schema and table data from a BACPAC file (.bacpac) into a new or empty database in SQL Server or Azure SQL Database. At the time of the import operation to an existing database the target database cannot contain any user-defined schema objects. Alternatively, a new database can be created by the import action when the authenticated user has [create database permissions](../../t-sql/statements/create-database-transact-sql.md#permissions).
 
+
+> [!NOTE]
+> SqlPackage import performs best for databases under 200GB. For larger databases, you may want to optimize the operation using properties available in this article and tips in [Troubleshooting with SqlPackage](./troubleshooting-issues-and-performance-with-sqlpackage.md).
+
 ## Command-line syntax
 
 **SqlPackage.exe** initiates the actions specified using the parameters, properties, and SQLCMD variables specified on the command line.  
