> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/databases/microsoft-sql-server/metadata-extracted.md).

# Microsoft SQL Server Metadata Extracted

Secoda pulls the following metadata from Microsoft SQL Server:

* Tables and Views
  * Name
  * Description
  * Schema
  * Database
* Columns
  * Name
  * Description
  * Type
  * Sort Order
  * Foreign Key
  * Primary Key
* Column Profile
  * Min
  * Max
  * Median
  * STD Deviation
  * Value Distribution
  * Statistic Value Count
  * Percent Filled
  * Unique
* MS SQL Stored Procedures
  * Creates lineage between the tables that are in the stored procedure
  * Adds the stored procedure under the Queries tab of the associated tables
* Lineage
  * MS SQL Table <-> MS SQL Table
  * MS SQL Column <-> MS SQL Column
  * MS SQL Column <-> MS SQL View
  * MS SQL Table <-> MS SQL Table
  * MS SQL Table/View <-> Tables from other sources
  * MS SQL Table/View <-> Dashboards from other sources
  * MS SQL Table/View <-> Jobs from other sources
* Preview on first 50 rows (Optional)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.secoda.co/integrations/databases/microsoft-sql-server/metadata-extracted.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.