No not, SQL Server 2008 but rather how the version numbers are tracked. Run SELECT @@VERSION or SELECT SERVERPROPERTY(’productversion’) if you’re not sure where this comes from.

 In 2005 and earlier, the version format looked something like M.mm.BBBB.rr

where

M is the major version number
mm is the minor version number
BBBB is the build number
rr is the build revision number

With SQL Server 2008, the format is now M.m.BBBB.rr where the minor version number will only display 1 zero and the revision number will only display 1 digit if it’s only a single digit revision. For example, the November CTP is 10.0.1075.23

Most of us really just cared about the major and build numbers since MS did away with .5 releases a long time ago. The build number tells us what service packs and/or hotfixes have been applied.

If your application checks for SQL Server version information during setup and has a tight dependency on the format of the string returned, remember to update your setup checker so it doesn’t disallow install for the wrong reason.

We had a few ISVs encounter this so far and while the change is a really tiny one (took a whole 30 seconds to fix) the app won’t install otherwise. Not that big of a deal but your users might get a little annoyed if your app’s setup complains about the wrong version in its error message (because it incorrectly interprets the new version number format) when users are using the right one.

 

joe yong