# Local hotspot detection is not working for SQL/SQL projects in Visual Studio – is it supported?

**URL:** <https://community.sonarsource.com/t/local-hotspot-detection-is-not-working-for-sql-sql-projects-in-visual-studio-is-it-supported/141924>\
**Category:** SonarQube Server / Community Build\
**Created:** [May 28, 2025, 5:09am UTC](https://community.sonarsource.com/t/local-hotspot-detection-is-not-working-for-sql-sql-projects-in-visual-studio-is-it-supported/141924 "2025-05-28T05:09:07Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![janani](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@janani](https://community.sonarsource.com/u/janani)\
**Post date:** [May 28, 2025, 5:09am UTC](https://community.sonarsource.com/t/local-hotspot-detection-is-not-working-for-sql-sql-projects-in-visual-studio-is-it-supported/141924/1 "2025-05-28T05:09:07Z")

</div>

Hi Team,

We are using **SonarQube Enterprise Edition v2025.1 (build 102418)** in Connected Mode with Visual Studio 2022 and the SonarQube for Visual Studio extension (v8.19).

Our project is a **SQL/T-SQL solution (e.g., SQLDACPAC)**, and we’re trying to understand the current support for:

- **Security Hotspot Detection**
- **Code Analysis / Taint Vulnerability detection**
- **Quality Gate enforcement for SQL**

We noticed that:

- No security hotspots or taint issues appear in Visual Studio.
- The SonarQube UI and local panes remain empty after analysis.
- There is limited/no documentation on SQL language support for static analysis or hotspots.

Could you please confirm:

1. Is **T-SQL (Transact-SQL)** supported for security hotspot detection or static analysis in SonarQube 2025.1?
2. If not yet supported, are there any workarounds or future plans to add SQL/T-SQL static analysis features?

Thank you for your help!

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [May 29, 2025, 7:48am UTC](https://community.sonarsource.com/t/local-hotspot-detection-is-not-working-for-sql-sql-projects-in-visual-studio-is-it-supported/141924/2 "2025-05-29T07:48:43Z")

</div>

Hey there!

SonarQube Server supports analyzing T-SQL code. You should make sure that you have [configured the file extensions](https://docs.sonarsource.com/sonarqube-server/latest/analyzing-source-code/languages/t-sql/#important-note) correctly for SonarQube to analyse your code as T-SQL (instead of PL/SQL). Concretely that means adding `.sql` to `sonar.tsql.file.suffixes` and removing `sql` from `sonar.plsql.file.suffixes`.

You can find a list of supported rules either in your instance, or [here](https://rules.sonarsource.com/tsql/).

~~SonarQube for Visual Studio does not support analyzing T-SQL Code at this point. You can voice you’re interested [on this roadmap item](https://portal.productboard.com/sonarsource/4-sonarqube-for-ide/c/201-support-t-sql-in-visual-studio?&utm_medium=social&utm_source=share)!~~

---

<div class="post-metadata">

**Author:** ![janani](https://avatars.discourse-cdn.com/v4/letter/j/f14d63/32.png) [@janani](https://community.sonarsource.com/u/janani)\
**Post date:** [May 29, 2025, 4:04pm UTC](https://community.sonarsource.com/t/local-hotspot-detection-is-not-working-for-sql-sql-projects-in-visual-studio-is-it-supported/141924/3 "2025-05-29T16:04:57Z")

</div>

[SonarQube for IDE: Visual Studio 8.11 - HTML and T-SQL support, AI CodeFix suggestions diff view](https://community.sonarsource.com/t/sonarqube-for-ide-visual-studio-8-11-html-and-t-sql-support-ai-codefix-suggestions-diff-view/134886) - here they have mentioned that T-SQL is now supported in the latest version of SonarQube for Visual Studio 8.11. I am using SonarQube visual studio 8.19 , Still it doesn’t show any hotspot in VS 2022 IDE

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [June 3, 2025, 10:22am UTC](https://community.sonarsource.com/t/local-hotspot-detection-is-not-working-for-sql-sql-projects-in-visual-studio-is-it-supported/141924/4 "2025-06-03T10:22:27Z")

</div>

Whoops, I missed the part where that card said released. 😆

Indeed, T-SQL analysis should be possible if you are using Connected Mode.

As I mentioned earlier:

> [@Colin](#):
>
> You can find a list of supported rules either in your instance, or [here](https://rules.sonarsource.com/tsql/).

Are you sure your code is triggering one of these rules? Can you give an example?

My understanding (based on the [docs](https://docs.sonarsource.com/sonarqube-for-ide/visual-studio/using/security-hotspots/#hotspot-analysis)) is that local Hotspot detection (all [4 of them](https://rules.sonarsource.com/tsql/type/Security%20Hotspot/)) is not supported for T-SQL. Let me double check with the responsible team to confirm.

> It is possible to locally detect and report hotspots in SonarQube for Visual Studio for C, C++, and JS/TS languages.

---

<div class="post-metadata">

**Author:** ![georgii.borovinskikh](https://avatars.discourse-cdn.com/v4/letter/g/9fc348/32.png) [@georgii.borovinskikh](https://community.sonarsource.com/u/georgii.borovinskikh)\
**Post date:** [June 4, 2025, 8:13am UTC](https://community.sonarsource.com/t/local-hotspot-detection-is-not-working-for-sql-sql-projects-in-visual-studio-is-it-supported/141924/8 "2025-06-04T08:13:55Z")

</div>

Hi @janani

Could you please provide the full verbose extension logs with the problem? [Troubleshooting - SonarQube for Visual Studio Documentation](https://docs.sonarsource.com/sonarqube-for-ide/visual-studio/troubleshooting/#how-to-get-sonarqube-for-vs-logs)  
If possible, please provide a reproducer to the problem

I can see T-SQL hotspots reported locally, but I’m not using a `.dacpac` project but rather a normal `.csproj` with a tsql file in it.

I see 2 possibilities:

1. We are not handling `.dacpac` projects correctly, or
2. There is actually no hotspot where you may expect it to be
