Match databaseversionno in $ndo$dbproperty with build no.

Chris86

We're currently planning to create a small tool which is monitoring SQL Server instances storing NAV databases and creating the NAV Service and several shortcuts on a terminal server. Therefor our approach was to get the databaseversionno from the $ndo$dbproperty table to identify the NAV version.

Unfortunately we're not able to match databaseversionno to the exact build no.

I searched at google and found some lists which tried to match databaseversionno and NAV version, but not at build level. Is there any way or any other suggestion?

Slawek_Guzek

Hi,

There is no 1 to 1 mapping between databaseversionno and client build numbers.

There are many client builds which are compatible with a single databaseversionno.

If you look at platform hotfixes list at Microsoft site you would see that only a few have a note attached to them saying that when the patch is installed the database needs to be upgraded. This is when the databaseversionno is getting changed.

For example: NAV2009 R2, KB2763217 from October 2012, client build 6.0.33842, the note :

Note: Build 33842 requires a database conversion.

All builds since R2 RTM, which is build 32012, up to previous published build 33869 (292 published builds) work on the database with the same databaseversionno

Slawek

David_Singleton

Sadly it's not even 1:many, its actually many:many, so as well as there being multiple Builds that will work with a particular database version, there are also a handful of builds that will work with multiple database versions without forcing a database update.

Other than trial and error there is no real way to work out the mappings.