SqlServer. DacFx. x86
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.
See the version list below for details.
Install-Package Microsoft.SqlServer.DacFx.x86 -Version 130.3485.1
dotnet add package Microsoft.SqlServer.DacFx.x86 --version 130.3485.1
<PackageReference Include="Microsoft.SqlServer.DacFx.x86" Version="130.3485.1" />
paket add Microsoft.SqlServer.DacFx.x86 --version 130.3485.1
#r "nuget: Microsoft.SqlServer.DacFx.x86, 130.3485.1"
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.
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.
This package has no dependencies.
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:
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.