Skip to content

troubleshooting-import-export-sqlpackage.md

Latest commit

 

History

History
43 lines (32 loc) · 2.59 KB

troubleshooting-import-export-sqlpackage.md

File metadata and controls

43 lines (32 loc) · 2.59 KB
title Troubleshooting Import/Export with SqlPackage
description Learn how to troubleshoot import and export with SqlPackage.exe.
ms.prod sql
ms.prod_service sql-tools
ms.technology tools-other
ms.topic conceptual
ms.assetid 198198e2-7cf4-4a21-bda4-51b36cb4284b
author dzsquared
ms.author drskwier
ms.reviewer maghan; sstein
ms.date 5/5/2021

Troubleshooting Import/Export with SqlPackage

In some scenarios, import or export operations take longer than expected or fail to complete. The following are some frequently suggested tactics to troubleshoot import and export operations. While reading the specific documentation page for each action to understand the available parameters and properties is recommended, this article serves as a starting point in investigating SqlPackage Import or Export operations.

Overall strategies

As general guideline, better performance can be obtained via the .NET Core version of SqlPackage.exe.

For issues related to timeouts, the properties CommandTimeout and LongRunningCommandTimeout can be used to tune the connection between SqlPackage.exe and the SQL instance.

Diagnostics

Logs are essential to troubleshooting. Capture the diagnostic logs to a file with the /DiagnosticsFile:<filename> parameter.

Additional performance-related trace data can be logged by setting the environment variable DACFX_PERF_TRACE=true before running SqlPackage. To set this environment variable in PowerShell, use the following command:

Set-Item -Path Env:DACFX_PERF_TRACE -Value true

Import action tips

For imports that contain large tables or tables with many indexes, the use of /p:RebuildIndexesOfflineForDataPhase=True or /p:DisableIndexesForDataPhase=False may improve performance. These properties modify the index rebuild operation to occur offline or not occur, respectively. Those and other properties are available to tune the SqlPackage.exe Import operation.

Export action tips

As an alternative operation to obtain the database schema and data while skipping the schema validation, perform an Extract with /p:ExtractAllTableData=True and /p:VerifyExtraction=True.

In scenarios where 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. That and other properties are available to tune the SqlPackage.exe Export operation.

Next steps