Skip to main content

Sequential GUIDs with .NET 9

Sequential GUIDs (Globally Unique Identifiers) are a specific type of GUID that are optimized for scenarios where insertion order matters, especially in databases. Traditional GUIDs are randomly generated and can cause performance issues in systems where GUIDs are used as primary keys due to their lack of natural order.

Sequential GUIDs address this problem by maintaining some level of order, making them more efficient for certain use cases. Before .NET 9 I typically had 2 approaches to generate a sequential guid:

  • I let the database generate the sequential guid for me through the NEWSEQUENTIALID function:
  • I generate the id myself using a library like RT.Comb:

Starting from .NET 9 I have a new option to add to my list as the Guid class got a new method Guid.CreateVersion7(),  that returns sequential Guids, according to version 7 UUID RFC 9562. This means that they can be ordered and used as a database table primary key, for example, because the values won't be scattered.

Remark: If no DateTimeOffset is supplied,CreateVersion7() uses DateTimeOffet.UtcNow by default.

More information

Avoiding index fragmentation with sequential guids

Using GuidCOMB in SQL Server and PostgreSQL

NEWSEQUENTIALID (Transact-SQL) - SQL Server | Microsoft Learn

GitHub - richardtallent/RT.Comb: Creating sequential GUIDs in C# for MSSQL or PostgreSql

Guid.CreateVersion7 Method (System) | Microsoft Learn

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more