Skip to content
aiWikis.org

SQL Server Standard

Use SQL Server for Protocol5 and JustAnIota database work unless the owning project explicitly chooses another engine.

Metadata

FieldValue
Source siteaiwikis.org
Source URLhttps://aiwikis.org/
Canonical AIWikis URLhttps://aiwikis.org/files/aiwikis/wiki-global-coding-standards-sql-server-md-8ae640c1/
Source referencewiki/global/coding-standards/sql-server.md
File typemd
Content categoryllm-wiki
Last fetched2026-05-08T21:22:18.3035107Z
Last changed2026-05-08T02:36:59.1954645Z
Content hashsha256:8ae640c1b67ef49cee621ec085bfb8ea5765dc865a6917fdc897363ade758857
Import statusunchanged
Raw source layerdata/sources/aiwikis/wiki-global-coding-standards-sql-server-md-8ae640c1b67e.md
Normalized source layerdata/normalized/aiwikis/wiki-global-coding-standards-sql-server-md-8ae640c1b67e.txt

Current File Content

Structure Preview

  • SQL Server Standard
  • Schema
  • Population
  • Access

Raw Version

---
uai_id: "82ac9918-e5ac-4e01-b08f-8f523dacc817"
type: "database-standard"
owner: "AIWikis maintainers"
status: "reviewed"
source_system: "AIWikis.org global"
source_status: "local synthesis from Protocol5 and JustAnIota SQL Server implementation practice"
sensitivity: "public-safe source-side memory"
agent_use: "load for SQL Server schema, migration, population, vector, and ADO.NET work"
lineage:
  - "wiki/global/coding-standards/index.md"
  - "wiki/protocol5/index.md"
  - "wiki/justaniota/index.md"
source_trace:
  - "wiki/global/coding-standards/sql-server.md"
confidence: 0.84
confidence_label: "reviewed-local"
last_linted: "2026-05-08T00:00:00Z"
handoff_export: "include"
aliases:
  - "SQL Server Coding Standard"
  - "SQL Server Database Standard"
---

# SQL Server Standard

Use SQL Server for Protocol5 and JustAnIota database work unless the owning project explicitly chooses another engine.

## Schema

- Make DDL idempotent with `OBJECT_ID`, `COL_LENGTH`, `sys.indexes`, `sys.foreign_keys`, and `sys.check_constraints` guards.
- Use typed lookup tables for durable classifications.
- Use explicit relationship tables for many-to-many or self-referential word, concept, and feature links.
- Keep source text fields normalized for lookup; use indexed exact comparisons after cleanup.
- Prefer check constraints for invariant test-data cleanup, including lowercase corpus fields when that is the selected strategy.

## Population

- Separate schema preparation, deterministic metadata population, quality gates, and embedding generation.
- Store source table, key, selected source text column, descriptor text, model, version, source, dimensions, hash, and update timestamp for embeddings.
- Clear stale embedding references when selected source text, descriptor, model, version, source, or dimensions change.
- Keep long LM Studio or vector population runs resumable and bounded.

## Access

- Use parameterized ADO.NET queries from .NET.
- Prefer exact indexed predicates after data cleanup over per-row `LOWER(...)` or broad collation casts.
- Keep live data mutations out of ordinary read-only smoke tests.

Why This File Exists

This is a LLM Wiki memory file from aiwikis.org. It is shown here because AIWikis.org is demonstrating the real source files that make the UAIX / LLM Wiki memory system work, not only summarizing those systems after the fact.

Role

This file belongs to the source-side wiki layer. It preserves a focused concept, source proxy, graph record, or operating rule so the public site can cite reviewed conclusions without flattening every reason into a single long page.

Structure

The file is structured around these visible headings: SQL Server Standard; Schema; Population; Access. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.

Prompt-Size And Retrieval Benefit

Keeping this material in a separate file reduces prompt pressure because an agent can load this exact unit only when its role, source site, category, or hash is relevant. The surrounding index pages point to it, while this page preserves the full content for audit and exact recall.

How To Use It

  • Humans should read the metadata first, then inspect the raw content when they need exact wording or provenance.
  • LLMs and agents should use the source site, category, hash, headings, and related files to decide whether this file belongs in the active prompt.
  • Crawlers should treat the AIWikis page as transparent evidence and follow the source URL/source reference for authority boundaries.
  • Future maintainers should regenerate this page whenever the source hash changes, then review the explanation if the role or structure changed.

Update Requirements

When this source file changes, update the raw source layer, normalized source layer, hash history, this rendered page, generated explanation, source-file inventory, changed-files report, and any source-section index that links to it.

Related Pages

Provenance And History

  • Current observation: 2026-05-08T21:22:18.3035107Z
  • Source origin: current-source-workspace
  • Retrieval method: local-source-workspace
  • Duplicate group: sfg-394 (primary)
  • Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "SQL Server Standard",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/files/aiwikis/wiki-global-coding-standards-sql-server-md-8ae640c1/",
    "source_reference":  "wiki/global/coding-standards/sql-server.md",
    "file_type":  "md",
    "content_category":  "llm-wiki",
    "content_hash":  "sha256:8ae640c1b67ef49cee621ec085bfb8ea5765dc865a6917fdc897363ade758857",
    "last_fetched":  "2026-05-08T21:22:18.3035107Z",
    "last_changed":  "2026-05-08T02:36:59.1954645Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-394",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-05-08T21:22:18.3035107Z"
}