Document: vector properties not loaded by default in EF Core 11

[Copilot]

EF Core 11 introduces partial property loading: SqlVector<T> properties are excluded from SELECT by default, since vectors are large and rarely need to be read back after ingestion.

vector-search.md

• Added a [!NOTE] noting that prior to EF Core 11, vector properties were always loaded like any other property
• Updated SQL snippets in VECTOR_SEARCH() and hybrid search examples to reflect vector column no longer appearing in SELECT

whatsnew.md

• Added brief "Vector properties not loaded by default" entry under the SQL Server section with a minimal code example showing that vector columns are excluded from entity projections but can still be used in filters and orderings

breaking-changes.md

• Added a low-impact breaking change entry for SqlVector<T> properties no longer being loaded by default (tracking issue #37279)
• Mitigations section notes that an opt-in mechanism will be introduced later in the EF Core 11 release, and documents explicit projection as a workaround in the meantime

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[roji]

Add a low-impact breaking change note. For now, leave the "mitigation" section as TODO - we'll be introducing a mechanism to opt into loading vector properties later in the release.

[Copilot]

Add a low-impact breaking change note. For now, leave the "mitigation" section as TODO - we'll be introducing a mechanism to opt into loading vector properties later in the release.

Done in dc55ed9 — added a low-impact breaking change entry in breaking-changes.md for SqlVector<T> properties no longer being loaded by default (tracking issue #37279). The Mitigations section includes a [!NOTE] placeholder explaining that an opt-in mechanism will be introduced later in the EF Core 11 release, along with an explicit-projection workaround in the meantime.

[Copilot]

Pull request overview

Documents an EF Core 11 behavior change for SQL Server vector columns (SqlVector<T>): vector properties are excluded from entity materialization by default to avoid transferring large payloads unnecessarily.

Changes:

• Added a “Vector properties not loaded by default” note/section in EF Core 11 “What’s New”.
• Added a low-impact breaking change entry describing the new default behavior and mitigations.
• Updated SQL examples in the SQL Server vector search docs to reflect the new default projection.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
entity-framework/core/what-is-new/ef-core-11.0/whatsnew.md	Adds a SQL Server “What’s New” entry explaining default non-loading of vector properties with a short example.
entity-framework/core/what-is-new/ef-core-11.0/breaking-changes.md	Adds a low-impact breaking change entry for SqlVector<T> not being loaded by default and a projection-based mitigation.
entity-framework/core/providers/sql-server/vector-search.md	Adds a note about the new default behavior and updates SQL snippets to omit vector columns from entity projections.

---

You can also share your feedback on Copilot code review. Take the survey.