Release Notes
About manually updating the Configuration Database and Log Databases
Using the web-based Update Tool, Nodinite has built-in support for updating the Configuration database. The Log Databases, however, always need to be manually updated. The reasons for manually updating either type of database are:
- Security-related problems - A SQL DBA may be the only one with enough SQL rights to perform the operation.
- Long execution times - The Web-based Update Tool lacks support for long-running transactions, and for obvious reasons, you do not want to hog the client browser while waiting for the operation to succeed (or not).
- Parallel execution - If you have many Log Databases.
When you perform a manual update of the Nodinite databases, you should use the Nodinite Logging Service service account or an account that is a part of the sysadmin role on the target Microsoft SQL Server instance(s).
To perform a Manual update, click the update button ( or ). This operation opens a modal with a script. Execute this script from a command prompt running as the service account used for the Logging Service:
Example of the 'Manual update' buttons.
You must install the DACPAC binaries to execute the script, please review the SQL Server Package (DACPAC) user guide for additional information.
Update Modal Example
First, make sure to select the appropriate version for the update. The default version is the one with the highest number.
Config Database Example
The following is an example of the default options.
"C:\Program Files\Microsoft SQL Server\160\DAC\bin\SqlPackage.exe" /Action:Publish /TargetDatabaseName:"NodiniteConfig_Dev" /TargetServerName:"localhost" /SourceFile:"C:\Program Files\Nodinite\Nodinite Update\UpdateClient\App_Data\files\versions\6.1.0.37\Nodinite.ConfigDatabase.dacpac" /SourceEncryptConnection:true /TargetEncryptConnection:true /SourceTrustServerCertificate:false /TargetTrustServerCertificate:true /Properties:RegisterDataTierApplication=True /Properties:BlockOnPossibleDataLoss=False /Properties:BlockWhenDriftDetected=False /Properties:DropIndexesNotInSource=True /Properties:DropConstraintsNotInSource=True /Properties:ScriptNewConstraintValidation=False
Ignore DACPAC Options
New 6.1.0.4 Check the Ignore DACPAC Options checkbox to ignore database options like collation, recovery mode and more.
Log Database Example
"C:\Program Files\Microsoft SQL Server\160\DAC\bin\SqlPackage.exe" /Action:Publish /TargetDatabaseName:"NodiniteLog_Dev_20220104" /TargetServerName:"localhost" /SourceFile:"C:\Program Files\Nodinite\Nodinite Update\UpdateClient\App_Data\files\versions\6.1.0.37\Nodinite.LogDatabase.Full.dacpac" /SourceEncryptConnection:true /TargetEncryptConnection:true /SourceTrustServerCertificate:false /TargetTrustServerCertificate:true /Properties:RegisterDataTierApplication=True /Properties:BlockOnPossibleDataLoss=False /Properties:BlockWhenDriftDetected=False /Properties:PopulateFilesOnFilegroups=False /Properties:DropIndexesNotInSource=True /Properties:DropConstraintsNotInSource=True /Properties:ScriptNewConstraintValidation=False /v:CustomPathData="null" /v:CustomPathImagedata="null" /v:CustomPathIndex="null"
Ignore DACPAC Options
New 6.1.0.4 Check the Ignore DACPAC Options checkbox to ignore database options like collation, recovery mode and more.