# Using Visual Studio Code for Writing SQL Queries in Ignition

**URL:** <https://forum.inductiveautomation.com/t/using-visual-studio-code-for-writing-sql-queries-in-ignition/100473>\
**Category:** Ignition\
**Tags:** python, database, ignition81, scripting\
**Created:** [January 6, 2025, 11:15am UTC](https://forum.inductiveautomation.com/t/using-visual-studio-code-for-writing-sql-queries-in-ignition/100473 "2025-01-06T11:15:27Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [January 6, 2025, 4:07pm UTC](https://forum.inductiveautomation.com/t/using-visual-studio-code-for-writing-sql-queries-in-ignition/100473/2 "2025-01-06T16:07:41Z")

</div>

I don't think this is an idea worth pursuing. Ignition's named queries have their own parameter syntax which is unlikely to work in Visual Studio. In addition,

> [@Running sql script from Ignition](https://forum.inductiveautomation.com/t/running-sql-script-from-ignition/78478/2):
>
> JDBC doesn't officially support SQL scripts. Just statements. Some JDBC drivers implement some SQL scripting syntax, but you are kind of on your own. If you really need to run a script in your DB, use a stored procedure. An SP can be called with a single statement.

Your best bet would be to develop your SQL in whatever environment you want and then paste it into Ignition's Named Query editor, fix the parameters and test it there.

Regarding your error message, the user that VSC is running under doesn't appear to have rights to the Ignition folder. That's a Windows permissions issue.

---

_[View the full topic](https://forum.inductiveautomation.com/t/using-visual-studio-code-for-writing-sql-queries-in-ignition/100473)._