You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Deployment | Adds support for publish properties `/p:IgnorePreDeployScript` and `/p:IgnorePostDeployScript`. These properties default to `false` and when enabled result in the |
41
+
| Data virtualization | Adds support for objects related to [data virtualization](/azure/azure-sql/database/data-virtualization-overview?view=azuresql&tabs=sas&preserve) for Azure SQL Database in import, export, extract, and publish operations. |
42
+
| Data virtualization | Adds Azure SQL Database to the [publish with parquet files preview](sqlpackage-with-data-in-parquet-files.md), enabling the use of Azure Blob Storage and parquet files to import data to a database. Extracting data to parquet files is not available for Azure SQL Database as it depends on [functionality not available in Azure SQL Database](/azure/azure-sql/database/data-virtualization-overview?view=azuresql&tabs=sas&preserve#limitations), `CREATE EXTERNAL TABLE AS SELECT`. |
43
+
| Deployment | Adds support for publish properties `/p:IgnorePreDeployScript` and `/p:IgnorePostDeployScript`. These properties default to `false` and when enabled result in the deployment plan omitting the corresponding scripts. [GitHub issue](https://github.com/microsoft/DacFx/issues/647)|
42
44
| Permissions | Adds support for the permission `ALTER ANY EXTERNAL MIRROR` for Azure SQL Database and SQL database in Fabric. This permission is required to export a database that contains one or more [mirrored tables](/fabric/database/mirrored-database/azure-sql-database-limitations). [GitHub issue](https://github.com/microsoft/DacFx/issues/648)|
43
45
| Permissions | Adds support for the permissions `CREATE ANY EXTERNAL MODEL` and `ALTER ANY EXTERNAL MODEL` for SQL Server 2025. |
44
46
| Permissions | Adds support for the permission `ALTER ANY INFORMATION PROTECTION` for SQL Server 2025 and Azure SQL Database. |
45
-
| ScriptDom | Updated ScriptDom to version 170.0.44. |
46
-
47
+
| Platform | The SqlPackage .zip build .NET SDK is updated to 8.0.412 |
48
+
| ScriptDom | Updated ScriptDom to version 170.0.64. |
49
+
| ScriptDom | Updates the Data warehouse in Fabric platform to leverage the `TSqlFabricDWParser` in ScriptDom. |
| Deployment | Fixed an issue where clustered columnstore indexes were being created by first creating a clustered index, causing the deployment to incur additional overhead and time. [GitHub issue](https://github.com/microsoft/DacFx/issues/264)|
57
60
| Extract | Fixed an issue where extracting a database from SQL database in Fabric would result in unusable user definition scripts. [GitHub issue](https://github.com/microsoft/DacFx/issues/631)|
Copy file name to clipboardExpand all lines: docs/tools/sqlpackage/sqlpackage-download.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: "Download and Install SqlPackage for Windows, macOS, or Linux"
4
4
author: dzsquared
5
5
ms.author: drskwier
6
6
ms.reviewer: maghan
7
-
ms.date: 07/29/2025
7
+
ms.date: 07/30/2025
8
8
ms.service: sql
9
9
ms.subservice: tools-other
10
10
ms.topic: install-set-up-deploy
@@ -22,7 +22,7 @@ SqlPackage runs on Windows, macOS, and Linux, and is available to install throug
22
22
23
23
-**Version number:** 170.1.61
24
24
-**Build number:** 170.1.61.1
25
-
-**Release date:** July 29, 2025
25
+
-**Release date:** July 30, 2025
26
26
27
27
SqlPackage is developed and released for both .NET 8 and .NET Framework. Installing the .NET 8 SqlPackage version is recommended via the [convenient `dotnet tool` method](#installation-cross-platform), which is cross-platform and easy to update, or via the [portable self-contained .zip download](#installation-file-download-alternative). The .NET 8 SqlPackage releases benefit from the continual advances to the performance and scalability of .NET as part of the [focus on for modern applications](/dotnet/core/introduction#net-ecosystem), which contrasts to the maintenance support of .NET Framework for Windows. The .NET Framework version is only available as a [.msi Windows installer](#windows-net-framework).
28
28
@@ -111,10 +111,10 @@ SqlPackage is also prepared as a self-contained download for Windows, macOS, and
Copy file name to clipboardExpand all lines: docs/tools/sqlpackage/sqlpackage-with-data-in-parquet-files.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Tips for using SqlPackage with data stored in Azure Blob Storage
4
4
author: dzsquared
5
5
ms.author: drskwier
6
6
ms.reviewer: llali, randolphwest
7
-
ms.date: 04/17/2025
7
+
ms.date: 07/30/2025
8
8
ms.service: sql
9
9
ms.subservice: tools-other
10
10
ms.topic: conceptual
@@ -16,12 +16,14 @@ ms.custom:
16
16
17
17
# SqlPackage with data in Parquet files (preview)
18
18
19
-
This article covers SqlPackage support for interacting with data stored in Azure Blob Storage that is in Parquet format. For SQL Server 2022 and Azure SQL Managed Instance, preview support for [extract](#extract-export-data) and [publish](#publish-import-data) with data in Parquet files in Azure Blob Storage is available in SqlPackage 162.1.176 and higher. Azure SQL Database and SQL Server 2019 and earlier aren't supported. The [import](sqlpackage-import.md) and [export](sqlpackage-export.md) actions continue to be available for SQL Server, Azure SQL Managed Instance, and Azure SQL Database. Support for Parquet files in Azure Blob Storage continues to be generally available for [Azure Synapse Analytics](sqlpackage-for-azure-synapse-analytics.md).
19
+
This article covers SqlPackage support for interacting with data stored in Azure Blob Storage that is in Parquet format.
20
20
21
21
With [extract](#extract-export-data), the database schema (`.dacpac` file) is written to the local client running SqlPackage and the data is written to Azure Blob Storage in Parquet format. The data is stored in individual folders named with two-part table names. [CREATE EXTERNAL TABLE AS SELECT (CETAS)](../../t-sql/statements/create-external-table-as-select-transact-sql.md) is used to write the files in Azure Blob Storage.
22
22
23
23
With [publish](#publish-import-data), the database schema (`.dacpac` file) is read from the local client running SqlPackage and the data is read from or written to Azure Blob Storage in Parquet format.
24
24
25
+
For SQL Server 2022 and Azure SQL Managed Instance, preview support for [extract](#extract-export-data) and [publish](#publish-import-data) with data in Parquet files in Azure Blob Storage is available in SqlPackage 162.1.176 and higher. For Azure SQL Database, preview support for [publish](#publish-import-data) is available in SqlPackage 170.1.61 and higher. SQL Server 2019 and earlier isn't supported. The [import](sqlpackage-import.md) and [export](sqlpackage-export.md) actions continue to be available for SQL Server, Azure SQL Managed Instance, and Azure SQL Database. Support for Parquet files in Azure Blob Storage continues to be generally available for [Azure Synapse Analytics](sqlpackage-for-azure-synapse-analytics.md).
26
+
25
27
In SQL databases hosted in Azure, the extract/publish operations with Parquet files offer improved performance over import/export operations with `.bacpac` files in many scenarios.
26
28
27
29
## Extract (export data)
@@ -75,7 +77,7 @@ See [SqlPackage publish](sqlpackage-publish.md#examples) for more examples of au
75
77
76
78
### PolyBase
77
79
78
-
[PolyBase](../../relational-databases/polybase/polybase-guide.md) is required for SqlPackage operations with Parquet files. The following query can be used to check if PolyBase is enabled:
80
+
For SQL Server and Azure SQL Managed Instance, [PolyBase](../../relational-databases/polybase/polybase-guide.md) is required for SqlPackage operations with Parquet files. The following query can be used to check if PolyBase is enabled:
79
81
80
82
```sql
81
83
// configuration_id =16397 is 'allow polybase export'
0 commit comments