> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/10.3/analyzing-source-code/languages/t-sql.md).

# T-SQL

*T-SQL analysis is available starting in* [*Developer Edition*](https://www.sonarsource.com/plans-and-pricing/developer/)*.*

## Language-specific properties <a href="#language-specific-properties" id="language-specific-properties"></a>

Discover and update the T-SQL-specific [Analysis parameters](/sonarqube-server/10.3/analyzing-source-code/analysis-parameters.md) in **Administration > General Settings > Languages > T-SQL**.

## Important note <a href="#important-note" id="important-note"></a>

With the default configuration, only files with the `.tsql` are analyzed as T-SQL, and files with the `.sql` file extension are analyzed as PL/SQL. This behavior is defined in **Administration > General Settings > T-SQL > File Suffixes** and **Administration > General Settings > PL/SQL > File Suffixes**. You can override these properties either at the server level or at the project level.


---

# 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:

```
GET https://docs.sonarsource.com/sonarqube-server/10.3/analyzing-source-code/languages/t-sql.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.