How do I Update a Log Database?
It's important for you to keep Nodinite updated since we always improve the product with new features, bug fixes making sure you get the best experience possible
Note: You must either run the steps detailed below as the Logging Service account or with an account with least equal rights.
If you are part of the SYSADMIN fixed server role on all instances hosting a Log Database you should have sufficient rights to execute the update steps.
- Start off with selecting the Environment to update:
List of environments installed, select the one to update
If the Manual update button is unavailable, then there is no update available and you can quit this guide here and now.
Click on the Manual update button to open a modal with the DACPAC command to execute:
Manual update button only available if there's an update to apply
Copy ALL of the content from the text box Copy the command text, to be repeated with unique settings for each log database
Note: There are two paths provided in the script, 1 for the SQLPackage.exe executable and the other for the DACPAC file.
- If you are going to execute the update script from another server you can simply click on the download button to get the DACPAC file required.
Note: The two paths must certainly be modified if you intend to execute the script on another server, please modify and verify new script
You must update from a command prompt, the DACPAC is not intended to be updated using the SQL MMC
Note: This step assumes you run the command running a command prompt logged in on the Nodinite server where the Install and Update Tool is installed. It is possible to copy the DACPAC file to another server and adjust folder paths provided to suite the target environment.
- Open an administrative command prompt as either the account running the Logging Service or with another account with at least equal rights or an account part of the SYSADMIN fixed server role on the SQL instance with the Log Databases to update
- Paste the command string from step 2 and press enter
Note: You should see text rolling on screen as the update progresses, this process may take seconds for small databases up to hour(s) for large databases or SQL Servers with poor disk IO performance.
- Repeat "Step 2" and "this Step" for all Log Databases listed for update (with the Information button).
Note: The Configuration Database may also be listed with the Information button however this database should only be updated manually if there's problem executing the update from the Install and Update Tool.
Reality has hit even Nodinite. First and foremost this problem has everything to do with the simple fact that there may be multiple Log Databases scattered over several SQL Server instances even on different networks running with a plethora of different security related account settings. Also, these Log Databases may be very large, rebuilding indexes, changing tables and more can take hours to complete. Since the Install and Update Tool is a Web based interface there is no way of keeping a responsive GUI. Therefore, all in all, Nodinite Log Databases must be updated manually.
Common problems and FAQ for the Configuration Database not found on this page can be found in the troubleshooting page.
The most common problem is that the DACPAC on the Nodinite server with the Install and Update Tool has a different installed version. Find the
SQLPackage.exe usually this file is in another version folder.
|Version of Folder||SQL Version||Possible path|
|105||SQL Server 2008 R2||"C:\Program Files (x86)\Microsoft SQL Server\105\DAC\bin\SqlPackage.exe"|
|110||SQL Server 2012||"C:\Program Files (x86)\Microsoft SQL Server\110\DAC\bin\SqlPackage.exe"|
|120||SQL Server 2014||"C:\Program Files (x86)\Microsoft SQL Server\120\DAC\bin\SqlPackage.exe"|
|130||SQL Server 2016||"C:\Program Files (x86)\Microsoft SQL Server\130\DAC\bin\SqlPackage.exe"|
|140||SQL Server 2017||"C:\Program Files (x86)\Microsoft SQL Server\140\DAC\bin\SqlPackage.exe"|
|150||SQL Server 2019||"C:\Program Files (x86)\Microsoft SQL Server\150\DAC\bin\SqlPackage.exe"|