Repository navigation
GetSchema("DataTypes") does not return entries for JSON and VECTOR types #3833
Description
Describe the bug
SqlConnection.GetSchema("DataTypes") does not include rows for the built-in SQL Server types JSON and VECTOR.
To reproduce
using Microsoft.Data.SqlClient;
using var connection = new SqlConnection("Server=.;Database=master;Integrated Security=true;");
connection.Open();
var table = connection.GetSchema("DataTypes");
bool hasJson = table.Rows.Cast<DataRow>().Any(r => ((string)r["TypeName"]).Equals("json", StringComparison.OrdinalIgnoreCase));
bool hasVector = table.Rows.Cast<DataRow>().Any(r => ((string)r["TypeName"]).Equals("vector", StringComparison.OrdinalIgnoreCase));
Console.WriteLine($"JSON found: {hasJson}");
Console.WriteLine($"VECTOR found: {hasVector}");Actual: both return false
Expected: both types should be included
Further technical details
Microsoft.Data.SqlClient version: all versions, including prerelease
.NET target: all
SQL Server version: SQL Server 2025
Operating system: any
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
- Status
Activity
mdaigle commentedon Dec 8, 2025
cc @apoorvdeshmukh this looks like another vector enhancement
igor-tkachev commentedon Dec 8, 2025
Just to clarify, this isn’t only a vector-specific enhancement.
When new types are added to the provider, their metadata also needs to appear in
GetSchema("DataTypes"), because many tools that work with database metadata, both at runtime and for code generation, rely on this information.Since JSON and VECTOR are missing from the metadata, this is mostly about keeping provider type metadata in sync with newly supported types.
Thanks!
mdaigle commentedon Dec 9, 2025
Thanks @igor-tkachev, we have prioritized it accordingly and will try to pick up the work soon.
priyankatiwari08 commentedon Sep 17, 2026
/triage
github-actions commentedon Sep 17, 2026
🔍 Triage Summary (on-demand re-triage)
Area\VectorAnalysis
SqlConnection.GetSchema("DataTypes")is missing rows for both thejsonandvectorSQL Server 2025 types. Thejsonhalf of this gap has already been addressed: #4592 was fixed by PR #4682, which switches thejsonrow's inclusion check from a raw server-version string comparison (SqlMetaDataFactory.SupportedByCurrentVersion) to the negotiatedConnectionCapabilities.JsonTypefeature flag, sojsonshould now correctly appear when the server advertises support (including Azure SQL). However,SqlMetaDataFactory.DataTypes.csstill has no row/branch forvectorat all — unlikejson, there is noAddVectorType-style conditional entry gated on a negotiated vector-support capability. This is a P2 metadata-completeness gap: it doesn't break core functionality, but it affects any tool or ORM that discovers supported types viaGetSchema("DataTypes"), including code-generation and schema-introspection scenarios noted by the reporter.Next Steps
jsonfix (PR Fix | GetSchema("DataTypes") does not report json type on Azure SQL (… #4682, merged 2026-09-14) resolves thejsonportion of this issue in the next release; if so, this issue's scope narrows tovectoronly.vectorrow toSqlMetaDataFactory.DataTypes.cs, following the same pattern used forjson: gate inclusion on a negotiated vector-support signal (e.g. an equivalent ofConnectionCapabilities.JsonType, mirroringTdsEnums.VECTOR_VERSION_NOT_SUPPORTEDchecks used elsewhere in the vector feature work) rather than a raw server version string comparison, so it works correctly against both on-prem SQL Server 2025 and any future Azure SQL vector support.DataTypesschema tests (functional or manual) asserting bothjsonandvectorrows appear when the server capability is negotiated, and are absent otherwise.ref/DataTypes documentation/samples if the row's metadata (e.g.IsBestMatch, literal prefixes) needs adjustment forvector.