Hybrid code search on Azure SQL and SQL Server 2025, end to end
Source files in, ranked answers out, one database, no separate vector store. Roslyn
chunking on statement boundaries, DiskANN, RRF across three retrieval legs, cross-encoder reranking,
and a relevance gate. Including the one place the two platforms genuinely diverge:
VECTOR_SEARCH has two mutually unparseable grammars and the version key that tells you
which to use is missing on self-hosted.