Guided tour

FabrCore 2.0 · Release and package availability

These guides track the current 2.0 source. Stable 2.0.0 publication is pending; package commands show the release target. Until it is published, follow the source quick start or use a matching available prerelease set. Release migration · Runtime modes

MODULE 08 · LESSON 8.1

Enable the SQL feature database

Enable persistence, ACL and knowledge services with the feature database.

Lesson 43 of 86 · FabrCore 2.0

Overview

ConnectionStrings:FabrCore enables the integrated SQL feature set. The database must already exist and support the expected schema/vector/graph capabilities. FabrCore validates it rather than silently changing incompatible columns or degrading a failed deployment to standalone.

The feature connection selects more than a storage backend

ConnectionStrings:FabrCore activates the integrated SQL feature set, including Orleans defaults, ACL, Memory and GraphRAG services. That is broader than choosing an Orleans persistence provider. Existing explicit Orleans overrides can still take precedence. A configured but invalid SQL connection fails startup instead of silently switching the application back to standalone memory.

Readiness includes schema and model prerequisites

The database must exist and support the required graph/vector schema. Startup initializes or validates the selected objects and required model aliases. Configure a compatible embeddings model and default chat model even before attaching a knowledge plugin to an agent. Successful schema readiness is not a paid inference test, and enabling a service does not automatically connect every agent to it.

Select SQL runtime mode

Provision a compatible SQL Server 2025/Azure SQL database and configure ConnectionStrings:FabrCore through a protected provider.
Configure default chat and compatible embeddings aliases. Use automatic schema initialization or set FabrCore:Database:AutoInitialize=false after applying supported migrations.
Restart and check readiness/capabilities. Select Memory/GraphRAG plugins explicitly for agents that need them; availability does not attach them to every agent.

SQL · reference snippet

{
  "ConnectionStrings": {
    "FabrCore": "Server=localhost;Database=fabrcore;Integrated Security=true;TrustServerCertificate=true"
  }
}

SQL · reference snippet

{
  "FabrCore": {
    "Database": {
      "ConnectionStringName": "FabrCore",
      "AutoInitialize": false
    }
  }
}

A Cloud Server can supply ConnectionStrings:FabrCore through the optional flat settings map when cloud settings are enabled. This still requires a reachable pre-existing compatible database and the required model catalog. It does not create a database server or make the switch live.

Merge the fragment into the effective envelope and resolve the connection secret through protected server storage. Environment/command-line overrides can take precedence over this map.

Discover settings/catalog and review restart requirements for the feature connection.
Publish the protected connection and compatible model configuration for staging, changing the effective version.
Restart deliberately and perform the readiness and persisted-record checks below. A pending-restart status is not a failed publication or proof of active SQL mode.

Cloud envelope fragment · merge with the model configuration

{
  "settings": {
    "ConnectionStrings:FabrCore": "<protected-compatible-SQL-connection>"
  }
}

Inspect effective source and pending restart settings

GET /fabrcoreapi/admin/v1/settings/catalog
Authorization: Bearer <administration-credential>

Prove durability with a recognizable record

Configure a development SQL database using the documented schema prerequisites, then start the Host. Expect readiness or a specific connection/schema/model configuration error; investigate that error before testing chat.
Create a disposable agent and save a recognizable state value. Restart the entire Host using the same database and identifiers, then read the value again.
Inspect capabilities to confirm the SQL features are advertised. Do not infer ACL/knowledge readiness solely from a successful HTTP listener or an Orleans storage table.

The persisted record establishes restart recovery for that path. Capability/readiness checks separately establish which integrated services are available.

If the result is different

Inspect the named schema/index/vector mismatch on startup. A version marker alone does not prove schema compatibility; never drop data to hide a failed check.

Go deeper

Explore the related documentation.