Definition of minor version numbers

Question

Post reply

Definition of minor version numbers

terry.musser

SSC Enthusiast

Points: 187
More actions
March 4, 2019 at 3:32 pm

#382857

I've noticed 2 different minor version numbers. I'm trying to understand why this is, what it means, etc.
For example, SQL Server 2016 SP1
2 minor version numbers 13.0.4001.0 and 13.1.4001.0
What does the .0 and .1 mean? Where can I learn more about this.
Thanks!
Terry Musser

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Gamleur84 Default port Points: 1475 More actions · Answer 1

Gamleur84

Default port

Points: 1475

March 4, 2019 at 7:25 pm

#2023520

It means Service Pack.

Sue_H SSC Guru Points: 90860 More actions · Answer 2

terry.musser - Monday, March 4, 2019 3:32 PM
I've noticed 2 different minor version numbers. I'm trying to understand why this is, what it means, etc.
For example, SQL Server 2016 SP1
2 minor version numbers 13.0.4001.0 and 13.1.4001.0
What does the .0 and .1 mean? Where can I learn more about this.
Thanks!
Terry Musser

Generally it's just service packs,fixes and update levels.
How to determine the version, edition, and update level of SQL Server and its components

If your more concerned with the 13.1, 13.0 difference, the last portion of the numbers are the same, same patch levels. I've never read why they have those differences but I always thought it may be with express/localdb versions.

Sue

terry.musser SSC Enthusiast Points: 187 More actions · Answer 3

Thanks for the reply. Unfortunately, the minor version has nothing to do with the service pack level.

The standard product version format for SQL Server is MM.nn.bbbb.rr. Each segment is defined as: MM - Major version, nn - Minor version, bbbb - Build number, rr - Build revision number

In the following screenshot, see how both 13.0.4001.0 and 13.1.4001.0 are the same service pack level; SP1? This pattern of having 2 minor versions per service pack level started with SQL 2008.

Can someone explain why there are 2 minor version numbers for the same SP level?

See also: Microsoft SQL Server Versions List

Terry Musser

Steve Jones - SSC Editor SSC Guru Points: 736270 More actions · Answer 4

Like most software places, Microsoft is composed of people, who are not consistent in what they do.

Someone likely defined the build versions in some method and over time they realized this doesn't really matter and it's easy to forget.

Gamleur84 Default port Points: 1475 More actions · Answer 5

The original question was what does it mean. The answer is the service pack level.
Now your new question is why there are 2 minor version numbers for the same SP level. Then, I don't know 🙂

DinoRS SSCrazy Points: 2683 More actions · Answer 6

one represents the SQL Server Version and the other defines the file version so your SP information only applies to the file version not SQL Server Version.

Maybe Microsoft might assume that if your SQL Server is up and running you are more likely to check @@Version than file versions. However if you have a lot of Service Packs, eventually even want to slipstream updates into Installation Media, then you might be interested in seeing at a quick glance through the file version.

Note on the side: only files that have been changed with a Service Pack will reflect this information. Microsoft is not updating version info for all files when you install an SP.