SqlPackageExecutable - System Parameter
The System parameter SqlPackageExecutable is used by the Nodinite Logging Service and specifies the local path to the SQL Package executable (SQLPackage.exe
), also known as DACFRAMEWORK or DACPAC, for your installed version of Microsoft SQL Server. The SQL binaries must be installed, and the path must be identical on all Nodinite application servers running either the Install and Update Tool or the Logging Service.
When it's time to create a new Nodinite Log Database, the Logging Service uses sqlpackage.exe
to install and register the new database. If there is any issue with the DACFRAMEWORK, the new database will not be created, and data will continue to accumulate in the existing online Log Database. This can lead to performance issues and storage challenges, so ensuring the correct configuration is essential.
You can either use PowerShell or manually download and install the package.
winget install Microsoft.SqlPackage --location "C:\Program Files\Microsoft SQL Server\170\DAC\bin\"
Download and install the latest sqlpackage
System Parameter Name | Data Type | Values/Example | Comment |
---|---|---|---|
SqlPackageExecutable | string | Path to SQLPackage.exe | Use a version that matches the highest used version of SQL Server |
This feature was introduced in version 4.0.
Example Paths for SqlPackage
The following SQL Server versions are supported by Nodinite.
64 Bit
Version of Folder | SQL Version | Possible path | Comment |
---|---|---|---|
170 | SQL Server 2022 | "C:\Program Files\Microsoft SQL Server\170\DAC\bin\SqlPackage.exe" | This is where 170 versions get installed by default |
160 | SQL Server 2019 | "C:\Program Files\Microsoft SQL Server\160\DAC\bin\SqlPackage.exe" | This is where 160 versions get installed by default |
150 | SQL Server 2019 | "C:\Program Files\Microsoft SQL Server\150\DAC\bin\SqlPackage.exe" | |
140 | SQL Server 2017 | "C:\Program Files\Microsoft SQL Server\140\DAC\bin\SqlPackage.exe" | |
130 | SQL Server 2016 | "C:\Program Files\Microsoft SQL Server\130\DAC\bin\SqlPackage.exe" | |
120 | SQL Server 2014 | "C:\Program Files\Microsoft SQL Server\120\DAC\bin\SqlPackage.exe" | |
110 | SQL Server 2012 | "C:\Program Files\Microsoft SQL Server\110\DAC\bin\SqlPackage.exe" | |
105 | SQL Server 2008 R2 | "C:\Program Files\Microsoft SQL Server\105\DAC\bin\SqlPackage.exe" |
32 Bit
Version of Folder | SQL Version | Possible path |
---|---|---|
170 | SQL Server 2022 | "C:\Program Files\Microsoft SQL Server\170\DAC\bin\SqlPackage.exe" |
160 | SQL Server 2019 | "C:\Program Files\Microsoft SQL Server\160\DAC\bin\SqlPackage.exe" |
150 | SQL Server 2019 | "C:\Program Files (x86)\Microsoft SQL Server\150\DAC\bin\SqlPackage.exe" |
140 | SQL Server 2017 | "C:\Program Files (x86)\Microsoft SQL Server\140\DAC\bin\SqlPackage.exe" |
130 | SQL Server 2016 | "C:\Program Files (x86)\Microsoft SQL Server\130\DAC\bin\SqlPackage.exe" |
120 | SQL Server 2014 | "C:\Program Files (x86)\Microsoft SQL Server\120\DAC\bin\SqlPackage.exe" |
110 | SQL Server 2012 | "C:\Program Files (x86)\Microsoft SQL Server\110\DAC\bin\SqlPackage.exe" |
105 | SQL Server 2008 R2 | "C:\Program Files (x86)\Microsoft SQL Server\105\DAC\bin\SqlPackage.exe" |
Warning
Just because you have a folder with one of these identifiers does not guarantee you have a SQL Server instance of that version installed. Some folders are created by newer versions for backward compatibility, by Visual Studio or other tools, or may remain after an instance has been removed or upgraded.
One way to get the installed version of SQL Server:
Here's an example of a version of SQL Server.
Info
Remember to uninstall older versions if you install a newer version to avoid conflicts and ensure optimal performance.
Frequently Asked Questions
Find more solutions to common problems and the Nodinite System Parameters FAQ in the Troubleshooting user guide.
How do I change the value?
Changing a value for the pre-defined System Parameters is described in the generic 'How do I change the System Parameters' article.
You must have a user with the same password in the master or target server
If you encounter a problem deploying the databases using SQLPackage.exe, such as the exception below, update SSMS to version 17.3 or later.
You must have a user with the same password in master or target server
Download and install the latest sqlpackage