Housing must call a language model from SQL as part of a RAG prompt flow for lease FAQs. Which procedure supports sending those prompts?
Select an answer to reveal the explanation.
Short Explanation
sp_invoke_external_rest_endpoint is housing’s SQL doorbell to the language model—ring it with the RAG prompt, get the answer back.
Full Explanation
Housing should build RAG prompts with sp_invoke_external_rest_endpoint so SQL can call an external language-model endpoint as part of the lease-FAQ flow. That procedure is the supported SQL Server pattern for authenticated HTTP invocation from T-SQL, enabling municipal databases to send prompt payloads and receive model responses without leaving the data plane’s orchestration. Using only DBCC TRACEON with no external language-model call fails by concept because trace flags adjust engine diagnostics behavior and do not invoke REST language-model endpoints. Printing prompts to the SQL error log and never invoking an endpoint fails because logging is not a model call and produces no generated FAQ answer. Replacing SQL with handwritten sticky notes instead of calling a model fails by abandoning the automated RAG path the scenario requires. Exam caveat: sp_invoke_external_rest_endpoint still needs secure authentication (commonly managed identity), network allowlists, and careful handling of secrets—procedure choice alone does not make the call safe. Operationally, craft the RAG prompt in SQL or an adjacent service, invoke the endpoint via sp_invoke_external_rest_endpoint, validate HTTP success and payload shape, and monitor latency and failure rates for the housing lease-FAQ assistant.