---
title: "Discussion on \"Real-Time SQL Analysis in VS Code: Catch Dangerous Queries\" | Hashnode"
description: "Discussion on \"Real-Time SQL Analysis in VS Code: Catch Dangerous Queries\". Before You Save the File"
url: "https://hashnode.com/posts/real-time-sql-analysis-in-vs-code-catch-dangerous-queries/69b7dabaa9f2770683342a3f"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Real-Time SQL Analysis in VS Code: Catch Dangerous Queries](https://makroumi.hashnode.dev/real-time-sql-analysis-in-vs-code-catch-dangerous-queries?utm_source=hashnode&utm_medium=feed)

Before You Save the File

Mar 16 · 4 min read · makroumi.hashnode.dev  
Read the article

-   [#sql](https://hashnode.com/tag/sql)
-   [#vscode-extensions](https://hashnode.com/tag/vscode-extensions)
-   [#database](https://hashnode.com/tag/database)
-   [#security](https://hashnode.com/tag/security)
-   [#devtools](https://hashnode.com/tag/devtools)

## Written by

[Makroumi](https://hashnode.com/@makroumi)

@makroumi · Toronto, Canada

  
[View profile](https://hashnode.com/@makroumi)

Backend engineer. I write about the SQL patterns that take down production systems.

Backend engineer with a focus on SQL performance, database reliability, and the kind of bugs that only show up at 2am on a Saturday. I spent 18 months building SlowQL, an open source SQL static analyzer with 171 rules across security, performance, reliability, compliance, quality and cost. Zero dependencies. Completely offline. Built after watching one SELECT \* on a 10 million row table take down production for an entire weekend. I write about the SQL patterns that look fine in review and destroy you in production. Real incidents, real root causes, and how to catch them before they ship. If you work with databases at scale you've probably already seen most of what I write about. Hopefully a bit earlier than I did.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
