Microsoft SQL Server APIs
A collection of APIs and interfaces for interacting with Microsoft SQL Server.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Microsoft SQL Server APIs the way a machine reads it — 43 machine-readable artifacts across 21 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Microsoft SQL Server APIs scores 51.4/100 (developing), with a separate agent-readiness read of 52/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Microsoft SQL Server APIs
Each block below is one kind of artifact we hold for Microsoft SQL Server APIs. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 21
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
SQL Server Database Engine API
Native database engine APIs for connecting and executing queries against SQL Server.
SQL Server REST API
REST API for managing SQL Server resources in Azure.
SQL Server Management Objects (SMO)
.NET API for programmatically managing SQL Server instances and databases.
SQL Server Reporting Services (SSRS) API
REST API for managing and accessing SQL Server Reporting Services.
ODBC Driver for SQL Server
ODBC driver API for connecting applications to SQL Server.
JDBC Driver for SQL Server
JDBC driver for connecting Java applications to SQL Server.
SQL Server Analysis Services (SSAS) API
APIs for managing and querying SQL Server Analysis Services.
Azure SQL Database REST API
REST API for managing Azure SQL Database resources.
Azure SQL Managed Instance REST API
REST API for creating, configuring, and managing Azure SQL Managed Instances.
SQL Server External REST Endpoint Invocation
Native T-SQL stored procedure sp_invoke_external_rest_endpoint for calling external HTTPS REST endpoints directly from SQL Server 2025 and Azure SQL.
Data API Builder for SQL Server
Open-source tool that generates REST and GraphQL endpoints for SQL Server and Azure SQL databases from configuration, without writing custom API code.
ADO.NET Provider for SQL Server (Microsoft.Data.SqlClient)
The official .NET data provider for Microsoft SQL Server and Azure SQL databases, providing ADO.NET access to SQL Server.
OLE DB Driver for SQL Server
Stand-alone OLE DB data access API for connecting applications to SQL Server.
SQL Server Integration Services (SSIS) API
Programmable object model for building, managing, and executing ETL data integration packages in SQL Server.
Node.js Driver for SQL Server
Node.js driver (tedious/mssql) for connecting JavaScript and TypeScript applications to SQL Server and Azure SQL Database.
Python Drivers for SQL Server
Python drivers for connecting to SQL Server including the first-party mssql-python driver, pyodbc, and pymssql.
Go Driver for SQL Server
Microsoft Go driver (go-mssqldb) for connecting Go applications to SQL Server and Azure SQL Database using the TDS protocol.
PHP Drivers for SQL Server
Microsoft Drivers for PHP for SQL Server providing SQLSRV and PDO_SQLSRV extensions for connecting PHP applications to SQL Server.
Ruby Driver for SQL Server
Ruby driver (TinyTDS) for connecting Ruby applications to SQL Server using FreeTDS DB-Library bindings.
Entity Framework Core SQL Server Provider
Entity Framework Core database provider enabling .NET object-relational mapping with SQL Server and Azure SQL databases.
SQL Server PowerShell Module
PowerShell cmdlets for managing SQL Server instances, databases, and resources from the command line.
Scroll within the panel for all 21 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
sql-server-mcp.yml
MCP SERVERGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Microsoft SQL Server APIs GraphQL API
Open-source tool that generates REST and GraphQL endpoints for SQL Server and Azure SQL databases from configuration, without writing custom API code.
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Sql Server Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Sql Server Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
T-SQL Query Engine
Full-featured relational database engine with comprehensive T-SQL support for queries, stored procedures, and functions.
Always On Availability Groups
High availability and disaster recovery with automatic failover for mission-critical databases.
In-Memory OLTP
Memory-optimized tables and natively compiled stored procedures for high-throughput transaction processing.
PolyBase
Query external data sources including Hadoop, Azure Blob Storage, and Oracle using T-SQL.
SQL Server Reporting Services
Enterprise reporting platform for creating, managing, and delivering paginated reports.
SQL Server Integration Services
ETL platform for building data integration and transformation packages.
Data API Builder
Generate REST and GraphQL endpoints from database tables and views without custom code.
External REST Endpoint Invocation
Call external HTTPS REST APIs directly from T-SQL using sp_invoke_external_rest_endpoint.
Scroll within the panel for all 8 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Sql Server Trust Center
SOC 1, SOC 2, SOC 3, ISO 27001, ISO 27017, ISO 27018, PCI DSS, HIPAA / HITRUST, FedRAMP, GDPR, CSA STAR
SECURITYUse Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Enterprise Data Management
Store and manage enterprise data with ACID compliance, security, and high availability.
Business Intelligence
Build BI solutions with reporting services, analysis services, and data integration.
Cloud Database Migration
Migrate on-premises SQL Server databases to Azure SQL Database or Managed Instance.
Application Backend
Use SQL Server as the data tier for web, mobile, and enterprise applications.
Data Warehousing
Build data warehouses with columnstore indexes, partitioning, and ETL pipelines.
Resources
Every other property we hold for Microsoft SQL Server APIs — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Learn 2
Tutorials, courses, talks, and written guidance
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/sql-server · machine-readable index on apis.io