Excalibur.Data.IdentityMap.SqlServer 10.0.0-alpha.15

This is a prerelease version of Excalibur.Data.IdentityMap.SqlServer.
dotnet add package Excalibur.Data.IdentityMap.SqlServer --version 10.0.0-alpha.15
                    
NuGet\Install-Package Excalibur.Data.IdentityMap.SqlServer -Version 10.0.0-alpha.15
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Excalibur.Data.IdentityMap.SqlServer" Version="10.0.0-alpha.15" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Excalibur.Data.IdentityMap.SqlServer" Version="10.0.0-alpha.15" />
                    
Directory.Packages.props
<PackageReference Include="Excalibur.Data.IdentityMap.SqlServer" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Excalibur.Data.IdentityMap.SqlServer --version 10.0.0-alpha.15
                    
#r "nuget: Excalibur.Data.IdentityMap.SqlServer, 10.0.0-alpha.15"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Excalibur.Data.IdentityMap.SqlServer@10.0.0-alpha.15
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Excalibur.Data.IdentityMap.SqlServer&version=10.0.0-alpha.15&prerelease
                    
Install as a Cake Addin
#tool nuget:?package=Excalibur.Data.IdentityMap.SqlServer&version=10.0.0-alpha.15&prerelease
                    
Install as a Cake Tool

Excalibur.Data.IdentityMap.SqlServer

SQL Server implementation of the Excalibur aggregate identity map store.

Setup

1. Create the table

CREATE TABLE [dbo].[IdentityMap] (
    ExternalSystem  NVARCHAR(128) NOT NULL,
    ExternalId      NVARCHAR(256) NOT NULL,
    AggregateType   NVARCHAR(256) NOT NULL,
    AggregateId     NVARCHAR(256) NOT NULL,
    CreatedAt       DATETIMEOFFSET NOT NULL CONSTRAINT DF_IdentityMap_CreatedAt DEFAULT SYSUTCDATETIME(),
    UpdatedAt       DATETIMEOFFSET NOT NULL CONSTRAINT DF_IdentityMap_UpdatedAt DEFAULT SYSUTCDATETIME(),

    -- NONCLUSTERED is required, not a preference: this triple is 1280 bytes, past SQL Server's
    -- 900-byte CLUSTERED key cap and inside the 1700-byte NONCLUSTERED one. Declared CLUSTERED,
    -- the table is created with only a warning and then rejects any row whose key exceeds 900
    -- bytes -- so a long external id fails on first write rather than at deployment.
    CONSTRAINT PK_IdentityMap PRIMARY KEY NONCLUSTERED (ExternalSystem, ExternalId, AggregateType),
    INDEX CIX_IdentityMap_External CLUSTERED (ExternalSystem, ExternalId),
    INDEX IX_IdentityMap_AggregateId (AggregateType, AggregateId)
);

2. Register the provider

services.AddIdentityMap(identity =>
{
    identity.UseSqlServer(sql =>
    {
        sql.ConnectionString(connectionString)
           .SchemaName("dbo")
           .TableName("IdentityMap");
    });
});

Features

  • No TVPs required -- batch lookups use parameterized IN clauses
  • Configurable batch size -- default 100, automatically chunks larger batches
  • MERGE-based upsert -- atomic bind operations
  • Conflict detection -- TryBind detects duplicate key violations and returns existing mappings

License

This project is multi-licensed under:

See LICENSE for details.

Database schema

This package does not create its tables. The DDL ships inside the .nupkg under scripts/, and you apply it — so a schema change to your database is always something you did deliberately, never something a version upgrade did to you while you were not looking.

Script
scripts/CreateIdentityMapTable.sql

Apply them in filename order before starting the application, and again — for any new ones — before starting a new version after an upgrade.

The scripts/ folder lives inside the package, not in your build output. To read it:

# the package folder, then the scripts inside it
dotnet nuget locals global-packages --list
ls ~/.nuget/packages/excalibur.data.identitymap.sqlserver/<version>/scripts/

The folder is authoritative. If any list of scripts — including this one — disagrees with what is actually in the package you installed, the package is right.

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
10.0.0-alpha.15 49 10/11/2026
10.0.0-alpha.14 52 10/2/2026
10.0.0-alpha.13 60 9/29/2026
10.0.0-alpha.12 68 9/25/2026
10.0.0-alpha.11 66 9/15/2026
10.0.0-alpha.10 81 9/6/2026
10.0.0-alpha.9 76 8/31/2026
10.0.0-alpha.8 88 8/14/2026
10.0.0-alpha.7 86 8/13/2026
10.0.0-alpha.6 88 8/11/2026
10.0.0-alpha.5 80 8/10/2026
10.0.0-alpha.4 78 8/10/2026
3.0.0-alpha.216 90 6/30/2026
3.0.0-alpha.215 84 6/23/2026
3.0.0-alpha.214 89 6/23/2026
3.0.0-alpha.208 83 6/11/2026
3.0.0-alpha.207 77 6/11/2026
3.0.0-alpha.205 78 6/10/2026
3.0.0-alpha.204 84 6/8/2026
3.0.0-alpha.203 77 6/8/2026
Loading failed