updates for troubleshooting IE with sqlpackage

dzsquared · dzsquared · commit 2b44477d31ed · 2022-08-31T15:15:25.000-07:00
diff --git a/azure-sql/database/database-export.md b/azure-sql/database/database-export.md
@@ -27,7 +27,7 @@ When you need to export a database for archiving or for moving to another platfo
 ## Considerations
 
 - For an export to be transactionally consistent, you must ensure either that no write activity is occurring during the export, or that you are exporting from a [transactionally consistent copy](database-copy.md) of your database.
-- If you are exporting to blob storage, the maximum size of a BACPAC file is 200 GB. To archive a larger BACPAC file, export to local storage.
+- If you are exporting to blob storage, the maximum size of a BACPAC file is 200 GB. To archive a larger BACPAC file, export to local storage with SqlPackage.exe.
 - Exporting a BACPAC file to Azure premium storage using the methods discussed in this article is not supported.
 - Storage behind a firewall is currently not supported.
 - Immutable storage is currently not supported.
@@ -69,14 +69,18 @@ Exporting a BACPAC of a database from [Azure SQL Managed Instance](../managed-in
 
 We recommend the use of the SQLPackage utility for scale and performance in most production environments. You can run multiple sqlpackage.exe commands in parallel for subsets of tables to speed up import/export operations.
 
-To export a database in SQL Database using the [SQLPackage](/sql/tools/sqlpackage) command-line utility, see [Export parameters and properties](/sql/tools/sqlpackage#export-parameters-and-properties). The SQLPackage utility ships with the latest versions of [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms) and [SQL Server Data Tools for Visual Studio](/sql/ssdt/download-sql-server-data-tools-ssdt), or you can download the latest version of [SQLPackage](/sql/tools/sqlpackage/sqlpackage-download) directly from the Microsoft download center.
+To export a database in SQL Database using the [SQLPackage](/sql/tools/sqlpackage) command-line utility, see [Export parameters and properties](/sql/tools/sqlpackage#export-parameters-and-properties). The [SQLPackage](/sql/tools/sqlpackage/sqlpackage-download) utility is available for Windows, macOS, and Linux.
 
 This example shows how to export a database using sqlpackage.exe with Active Directory Universal Authentication:
 
 ```cmd
 sqlpackage.exe /a:Export /tf:testExport.BACPAC /scs:"Data Source=apptestserver.database.windows.net;Initial Catalog=MyDB;" /ua:True /tid:"apptest.onmicrosoft.com"
 ```
 
+## Azure Data Studio
+
+[Azure Data Studio](/sql/azure-data-studio) is a free, open-source tool and is available for Windows, Mac, and Linux.  The "SQL Server dacpac" extension provides a wizard interface to SqlPackage operations including export and import.  See the extension's [documentation page](/sql/azure-data-studio/extensions/sql-server-dacpac-extension) for more information on installing and using the extension.
+
 ## SQL Server Management Studio (SSMS)
 
 The newest versions of SQL Server Management Studio provide a wizard to export a database in Azure SQL Database or a SQL Managed Instance database to a BACPAC file. See the [Export a Data-tier Application](/sql/relational-databases/data-tier-applications/export-a-data-tier-application).
diff --git a/azure-sql/database/database-import-export-hang.md b/azure-sql/database/database-import-export-hang.md
@@ -31,17 +31,19 @@ The import and export operations don't represent a traditional physical database
 
 The Azure SQL Database Import/Export service provides a limited number of compute virtual machines (VMs) per region to process import and export operations. The compute VMs are hosted per region to make sure that the import or export avoids cross-region bandwidth delays and charges. If too many requests are made at the same time in the same region, significant delays can occur in processing the operations. The time that's required to complete requests can vary from a few seconds to many hours.
 
+Additionally, as the Import/Export service performs a logical backup of the database the time to complete is more dependent on the number of objects in the database than a traditional physical database backup.
+
 
 ## Recommended solutions
 
 If your database exports are used only for recovery from accidental data deletion, all the Azure SQL Database editions provide self-service restoration capability from system-generated backups. But if you need these exports for other reasons, and if you require consistently faster or more predictable import/export performance, consider the following options:
 
 * [Export to a BACPAC file by using the SQLPackage utility](./database-export.md#sqlpackage-utility).
+* [Export to a BACPAC file by using Azure Data Studio](./database-export.md#azure-data-studio).
 * [Export to a BACPAC file by using SQL Server Management Studio (SSMS)](./database-export.md#sql-server-management-studio-ssms).
 * Run the BACPAC import or export directly in your code by using the Microsoft SQL Server Data-Tier Application Framework (DacFx) API. For additional information, see:
   * [Export a data-tier application](/sql/relational-databases/data-tier-applications/export-a-data-tier-application)
   * [Microsoft.SqlServer.Dac Namespace](/dotnet/api/microsoft.sqlserver.dac)
-  * [Download DACFx](https://www.microsoft.com/download/details.aspx?id=55713)
 
 ## Things to consider when you export or import a database
 
diff --git a/azure-sql/database/database-import.md b/azure-sql/database/database-import.md
@@ -64,7 +64,7 @@ To migrate a database into an [Azure SQL Managed Instance](../managed-instance/s
 
 ## Using SqlPackage
 
-To import a SQL Server database using the [SqlPackage](/sql/tools/sqlpackage) command-line utility, see [import parameters and properties](/sql/tools/sqlpackage#import-parameters-and-properties). [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms) and [SQL Server Data Tools for Visual Studio](/sql/ssdt/download-sql-server-data-tools-ssdt) include SqlPackage. You can also download the latest [SqlPackage](https://www.microsoft.com/download/details.aspx?id=53876) from the Microsoft download center. 
+To import a SQL Server database using the [SqlPackage](/sql/tools/sqlpackage) command-line utility, see [import parameters and properties](/sql/tools/sqlpackage/sqlpackage-import). You can download the latest [SqlPackage](/sql/tools/sqlpackage/sqlpackage-download) for Windows, macOS, or Linux. 
 
 For scale and performance, we recommend using SqlPackage in most production environments rather than using the Azure portal. For a SQL Server Customer Advisory Team blog about migrating using `BACPAC` files, see [migrating from SQL Server to Azure SQL Database using BACPAC Files](/archive/blogs/sqlcat/migrating-from-sql-server-to-azure-sql-database-using-bacpac-files).
 
@@ -85,6 +85,10 @@ This example shows how to import a database using SqlPackage with Active Directo
 sqlpackage.exe /a:Import /sf:testExport.bacpac /tdn:NewDacFX /tsn:apptestserver.database.windows.net /ua:True /tid:"apptest.onmicrosoft.com"
 ```
 
+## Azure Data Studio
+
+[Azure Data Studio](/sql/azure-data-studio) is a free, open-source tool and is available for Windows, Mac, and Linux.  The "SQL Server dacpac" extension provides a wizard interface to SqlPackage operations including export and import.  See the extension's [documentation page](/sql/azure-data-studio/extensions/sql-server-dacpac-extension) for more information on installing and using the extension.
+
 ## Using PowerShell
 
 > [!NOTE]
@@ -160,12 +164,12 @@ Stop-AzSqlDatabaseActivity -ResourceGroupName $ResourceGroupName -ServerName $Se
 ## Limitations
 
 - Importing to a database in elastic pool isn't supported. You can import data into a single database and then move the database to an elastic pool.
-- Import Export Service does not work when Allow access to Azure services is set to OFF. However you can work around the problem by manually running sqlpackage.exe from an Azure VM or performing the export directly in your code by using the DACFx API.
+- Import Export Service does not work when Allow access to Azure services is set to OFF. However you can work around the problem by manually running sqlpackage.exe from an Azure VM or performing the export directly in your code by using the DacFx API.
 - Import does not support specifying a backup storage redundancy while creating a new database and creates with the default geo-redundant backup storage redundancy. To workaround, first create an empty database with desired backup storage redundancy using Azure portal or PowerShell and then import the BACPAC into this empty database. 
 - Storage behind a firewall is currently not supported.
 
 
-## Import using wizards
+## Additional tools
 
 You can also use these wizards.
 
@@ -174,6 +178,7 @@ You can also use these wizards.
 
 ## Next steps
 
+- To learn how to connect to and query Azure SQL Database from Azure Data Studio, see [Quickstart: Use Azure Data Studio to connect and query Azure SQL Database](/sql/azure-data-studio/quickstart-sql-database).
 - To learn how to connect to and query a database in Azure SQL Database, see [Quickstart: Azure SQL Database: Use SQL Server Management Studio to connect to and query data](connect-query-ssms.md).
 - For a SQL Server Customer Advisory Team blog about migrating using BACPAC files, see [Migrating from SQL Server to Azure SQL Database using BACPAC Files](https://techcommunity.microsoft.com/t5/DataCAT/Migrating-from-SQL-Server-to-Azure-SQL-Database-using-Bacpac/ba-p/305407).
 - For a discussion of the entire SQL Server database migration process, including performance recommendations, see [SQL Server database migration to Azure SQL Database](migrate-to-database-from-sql-server.md).
diff --git a/docs/azure-data-studio/quickstart-sql-database.md b/docs/azure-data-studio/quickstart-sql-database.md
@@ -1,5 +1,5 @@
 ---
-title: Connect and query an Azure SQL database
+title: Connect and query an Azure SQL Database
 description: Do a quickstart in which you use Azure Data Studio to connect to an Azure SQL Database server, and then create and query a database.
 ms.prod: azure-data-studio
 ms.technology: azure-data-studio
@@ -14,7 +14,7 @@ ms.custom:
   - intro-quickstart
 ms.date: 05/14/2019
 ---
-# Quickstart: Use Azure Data Studio to connect and query Azure SQL database
+# Quickstart: Use Azure Data Studio to connect and query Azure SQL Database
 
 In this quickstart, you'll  use Azure Data Studio to connect to an Azure SQL Database server. You'll then run Transact-SQL (T-SQL) statements to create and query the TutorialDB database, which is used in other Azure Data Studio tutorials.
 
