When an insight is invalidated due to a schema change — either because a DDL audit event was processed or because a fingerprint scan detected a mismatch — the old row is soft-deleted fromDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/A-Point-Systems-ltd/ms-sql-mcp/llms.txt
Use this file to discover all available pages before exploring further.
AIInsights.SchemaInsights and archived to AIInsights.InsightHistory. GetInsightHistory retrieves these archived rows so you can audit how an object’s insight has evolved over time and recover context that was discarded when the schema changed.
Parameters
Filter archived rows to a single schema. Pass
null to return history across all schemas.Filter archived rows to a single object name (exact match, no wildcards). Pass
null to return history for all objects.Maximum number of rows to return. Clamped server-side to the range
1–2000. Defaults to 100. Archived rows are returned newest-first.Returns
true when the query completed without error.Present when
success is true. Array of archived InsightHistory rows, newest archived row first.Present only when
success is false. Contains the exception message.GetInsightHistory requires USE_INSIGHTS_LAYER to be enabled (the default). When the layer is disabled, the tool returns an error indicating the layer is off.Archived rows are never deleted —
AIInsights.InsightHistory is an append-only audit log. Use GetInsightHistory to recover the authored description, businessPurpose, and usageGuidelines from a previous insight as a starting point when re-authoring after a schema change.