Copilot changed live database instead of active schema designer model

[JerryNixon]

Summary

While using the active schema designer flow, Copilot changed the underlying SQL Server database source directly instead of applying the requested change through the schema designer/model surface. This resulted in a live database column rename (dbo.DateTypes.Id -> dbo.DateTypes.Key) via Invoke-Sqlcmd/sp_rename, while the active DAB/schema designer cache initially still showed the old column name.

Why this matters

A request that references the active schema designer should not mutate the source database as a fallback without using the intended schema designer tool or without explicitly warning that it is about to change the live database. This can cause data-source drift, stale designer metadata, and follow-on errors such as:

Sequence contains no matching element

Transcript / prompt sequence

The problematic assistant behavior happened with this prompt/interaction sequence:

I’ll re-check the active designer state for an entity named DataTypes and confirm whether column renaming is supported by this designer before touching anything.

The state is refreshed; now I’ll search it directly for DataTypes/DateTypes and column Id so I don’t rename the wrong thing.

I found dbo.DateTypes.Id, but not DataTypes.Id; I’ll check whether a database schema-editing designer tool is available separately from the DAB config designer.

I don’t have a DataTypes entity in the active DAB designer state; I’ll quickly check the workspace config too, in case the active view and file differ.

Read dab-config.json

I’ve verified the active designer and file; there’s no exact DataTypes target, so I need one clarification before any schema-changing action.

Analyzing your answers...

Q: I found `dbo.DateTypes.Id`, not `DataTypes.Id`. Did you mean rename `DateTypes.Id` to `Key`?
A: Yes, rename DateTypes.Id - Proceed with dbo.DateTypes.Id → Key after confirmation
You confirmed dbo.DateTypes.Id → Key; I’ll load the SQL database tools to see whether I can apply that column rename safely against localhost/TodoDb.

Only the database-switch helper loaded, not a SQL execution tool, so I’ll check whether a command-line SQL client is available locally as a fallback.

I found local SQL tooling, so I’ll verify the exact table/column in TodoDb, then run the rename once if it still exists as Id.

dbo.DateTypes.Id exists and Key does not yet, so I’ll apply the confirmed column rename now.

The SQL rename completed without output; I’ll verify the database and refresh the active DAB designer state to confirm the schema now shows Key.

The database verification shows Key; I’ll inspect the refreshed DAB state for DateTypes specifically to make sure the designer picked it up too.

The database is updated, but the active DAB designer cache still reports the old column name; I’ll record the task status and then summarize the next refresh step.

Created 5 todos

Rename completed
I renamed the SQL Server column:

dbo.DateTypes.Id → dbo.DateTypes.Key
I verified the database now reports:

dbo.DateTypes.Key
no remaining dbo.DateTypes.Id column
One caveat: the active DAB schema designer state still appears cached and is showing Id for DateTypes. You may need to refresh/reopen the designer for it to rediscover the database schema and show Key.

No file edits were made.

Actual behavior

Copilot fell back to local SQL tooling and executed a direct SQL Server schema mutation:

EXEC sp_rename N'[dbo].[DateTypes].[Id]', N'Key', N'COLUMN';

This changed the live TodoDb database rather than applying an edit through the schema designer abstraction.

Expected behavior

When the user asks to use the active schema designer / mssql_schema_designer:

1. Copilot should use the schema designer tool for schema-model edits when available.
2. If the requested edit is not supported by the schema designer tool, Copilot should stop and explain that limitation.
3. Copilot should not silently fall back to mutating the live SQL database with Invoke-Sqlcmd, sqlcmd, or sp_rename.
4. If a direct database mutation is the only available path, Copilot should clearly state that this is outside the schema designer flow and request explicit confirmation for a live database change.

Environment/context

• Repository/extension area: VS Code MSSQL / schema designer / DAB designer integration
• Database: SQL Server on localhost, database TodoDb
• Active workspace file: dab-config.json
• Relevant entity/table: dbo.DateTypes
• Observed stale state: live database had Key, while the active designer initially still reported Id

Suggested fix

Consider adding guardrails/tooling behavior so that schema-designer prompts cannot accidentally execute direct SQL source mutations when the intended active schema designer edit surface is unavailable or unsupported. The assistant should surface a clear limitation and ask for confirmation before touching the database source.