Home/ Questions/Q 609821
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T17:36:27+00:00

The table I am working on has a primary key which is essentially a

  • 0

The table I am working on has a primary key which is essentially a version number. A couple of examples of the version number are below:

1.0.0.0
1.1.2.24

Varchar seemed the most obvious choice to me, but I’m looking to set the primary key as a clustered index – I have read on SQL performance sites that you should avoid using varchars in clustered primary keys due to paging issues.

Given the version number is of variable length, what would therefore be the most appropriate datatype for the column?

This database I’m working on is running SQL Server 2005.

Thanks for your help.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Well, you could always use four INT fields – MAJOR, MINOR, RELEASE and BUILD – together, those are 16 bytes like a GUID – not too bad.

    The only drawback to this approach is that if you need to reference this table in a foreign key constraint, you’ll have to join on all four tables, typically.

    I wouldn’t use VARCHAR – INT is better (typically faster). Also, due to the variable nature of VARCHAR, things can get a bit messy (VARCHAR fields can grow and cause all sorts of issues, while an INT always stays 4 bytes).

    The other quite popular option would be to have those four fields for the actual version, and an additional surrogate VersionID INT IDENTITY for optimal clustered key performance.

    • 0