Version 1.1.0.0 of Database Vault was released on 04.01.2016 as the initial release. This changelog records that milestone and will document all subsequent changes. Reviewing release history lets you verify compatibility, understand addressed issues, and schedule updates without disrupting production .NET applications on Windows servers.

Change logs exist to remove ambiguity. When operating hosted database environments you must know exactly when foundational capabilities arrived, when fixes were issued, and when configuration requirements changed. The entry below is the definitive record of the product's first availability.

#Release History

#Version 1.1.0.0

Released: 04.01.2016

Initial Release

The 1.1.0.0 release established the core binary set, configuration schema, and integration points with SQL Server on Windows. All later versions build directly on this foundation. Administrators who onboarded after this date should confirm their installed binaries match or exceed this baseline before applying additional patches.

#Understanding Versioning

Database Vault follows a major.minor.build scheme. The initial 1.1.0.0 release set the major version at 1, indicating a production-ready starting point rather than a beta. Minor increments add functionality without breaking existing stored procedures or connection strings. Build numbers address defects or minor operational refinements. Always match the major version of your application tier to the vault version to avoid authentication handshake failures.

In practice, version skew between web servers and the vault service is the most common cause of intermittent login errors. The release record removes guesswork by listing exact rollout dates so you can correlate against your own deployment timeline.

#Operational Guidance

Before applying any update, export the current vault configuration and back up the target databases. Test the new version against a staging environment that mirrors production load and .NET Framework version. Confirm that connection strings using the vault provider continue to resolve correctly and that audit logging levels remain consistent with your compliance requirements.

  • Validate service account permissions after upgrade; some builds tighten defaults.
  • Review any updated schema scripts shipped with the release.
  • Update client libraries in all dependent ASP.NET projects to the matching version.
  • Monitor error logs for the first 48 hours post-deployment.

#Checking Installed Version

Use the following T-SQL against the vault management database to confirm the deployed version. This query reads the metadata written during the initial 1.1.0.0 installation and any later updates.

tsql 
SELECT [Key], [Value]
FROM [dbo].[VaultMetadata]
WHERE [Key] = 'InstalledVersion';

Alternatively, from PowerShell on the web server you can inspect the loaded assembly:

powershell 
$assembly = [System.Reflection.Assembly]::LoadFrom("C:\Program Files\DatabaseVault\VaultProvider.dll")
$assembly.GetName().Version

Both methods return the full four-part version string. Compare it against the entries in this changelog to determine whether an update is required.

#Practical Takeaway

Start every deployment or audit by consulting this page first. The 1.1.0.0 initial release on 04.01.2016 remains the baseline; everything else layers on top. Bookmark this document, script the version-check queries into your deployment pipeline, and treat every new entry as a required reading before you touch production. For step-by-step installation and configuration instructions, see the Database Vault setup guide in the same knowledge base.