Microsoft.SqlServer.DacFx.x86 130.3485.1

.NET Framework 4.0
Suggested Alternatives


There is a newer version of this package available.
See the version list below for details.
NuGet\Install-Package Microsoft.SqlServer.DacFx.x86 -Version 130.3485.1
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
dotnet add package Microsoft.SqlServer.DacFx.x86 --version 130.3485.1
<PackageReference Include="Microsoft.SqlServer.DacFx.x86" Version="130.3485.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Microsoft.SqlServer.DacFx.x86 --version 130.3485.1
#r "nuget: Microsoft.SqlServer.DacFx.x86, 130.3485.1"
#r directive can be used in F# Interactive, C# scripting and .NET Interactive. Copy this into the interactive tool or source code of the script to reference the package.
// Install Microsoft.SqlServer.DacFx.x86 as a Cake Addin
#addin nuget:?package=Microsoft.SqlServer.DacFx.x86&version=130.3485.1

// Install Microsoft.SqlServer.DacFx.x86 as a Cake Tool
#tool nuget:?package=Microsoft.SqlServer.DacFx.x86&version=130.3485.1

The Microsoft SQL Server Data-Tier Application Framework (DACFx) is a component which provides application lifecycle services for database development and management for Microsoft SQL Server and Microsoft Azure SQL Databases.
     DacFX supports various database deployment and management scenarios for SQL Server and Microsoft Azure SQL Databases including extracting / exporting a live database to a DAC package, deploying a DAC package to a new or existing database, and migrating from on-premise SQL Server to Microsoft Azure. This functionality is exposed via the DACFx managed API. DACFx can target SQL Server 2008, 2008R2, 2012, 2014, 2016 and Microsoft Azure SQL Databases.
     This nuget package is a lightweight version of Dacfx. If you would like to use the command-line utility SqlPackage.exe for creating and deploying .dacpac and .bacpac packages, please download  DacFramework.msi from Microsoft download page.

Product Versions
.NET Framework net40 net403 net45 net451 net452 net46 net461 net462 net463 net47 net471 net472 net48
Compatible target framework(s)
Additional computed target framework(s)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories (2)

Showing the top 2 popular GitHub repositories that depend on Microsoft.SqlServer.DacFx.x86:

Repository Stars
R Tools for Visual Studio.
SIM is an open-source tool for managing the local park of Sitecore instances. You can install, locate, maintain, reinstall or delete Sitecore products.
Version Downloads Last updated
150.5282.3 4,782 10/4/2021
150.5164.1 1,763 6/2/2021
150.5084.2 1,734 3/10/2021
150.4897.1 2,151 9/18/2020
150.4826.1 846 6/24/2020
150.4769.1 1,182 5/12/2020
150.4573.2 18,817 10/28/2019
150.4538.1 2,288 9/14/2019
150.4532.1 689 9/5/2019
150.4384.2 33,186 4/16/2019
150.4316.1 19,928 2/5/2019
150.4200.1 11,817 10/25/2018
140.3881.1 44,169 1/3/2018
140.3745.1 102,600 7/10/2017
140.3727.2 1,209 6/30/2017
140.3652.3 3,198 4/19/2017
130.3485.1 80,915 10/26/2016
130.3450.1 6,097 9/21/2016
130.3411.1 9,681 8/15/2016
130.3370.2 1,812 6/30/2016
130.3352.1 2,207 6/13/2016

DacFx release 16.5 (released Oct 26, 2016).

SqlPackage and DacFx API Improvements

Using SqlPackage.exe and the DacFx APIs you can now generate a deployment report, deployment script, and publish to a database all in one action. This is a timesaver for anyone who likes to keep a report of what was published during a deployment. Another benefit is that for Azure scenarios, separate scripts for the master database and the deploy target database are created. Up to now a single script was created which was not useful for repeated deployments.

For SqlPackage’s Publish and Script actions, two new arguments have been added.

DeployScriptPath (shortname: dsp). This is an optional path to write the deployment script to. For Azure deployment, if there were TSQL commands to create of modify the DB a master script will be written to the same path but with “Filename_Master.sql” as the output file name.
DeployReportPath (shortname: drp). This is an optional path to write the deployment report to.
Note that for the Script action, either the existing Output Path arguments or the new script/report-specific arguments should be used, but not both.

Sample usage:

Publish Action Sqlpackage.exe /a:Publish /tsn:(localdb)\ProjectsV13 /tdn:MyDatabase /deployscriptpath:”My\DeployScript.sql” /deployreportpath:”My\DeployReport.xml”

Script Action Sqlpackage.exe /a:Script /tsn:(localdb)\ProjectsV13 /tdn:MyDatabase /deployscriptpath:”My\DeployScript.sql” /deployreportpath:”My\DeployReport.xml”

In DacFx, two new APIs have been added: DacServices.Publish() and DacServices.Script(). These also support performing publish + script + report actions in a single operation.