# SQL Execute Script Plugin

**URL:** <https://community.automationedge.com/t/sql-execute-script-plugin/1827>\
**Category:** Get Help & Discuss\
**Created:** [March 20, 2020, 9:44am UTC](https://community.automationedge.com/t/sql-execute-script-plugin/1827 "2020-03-20T09:44:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![komal.rayate](https://avatars.discourse-cdn.com/v4/letter/k/df705f/32.png) [@komal.rayate](https://community.automationedge.com/u/komal.rayate)\
**Post date:** [March 20, 2020, 9:44am UTC](https://community.automationedge.com/t/sql-execute-script-plugin/1827/1 "2020-03-20T09:44:04Z")

</div>

We do have ‘execute SQL Script’ plugin for all queries then when to use separate steps for insert, update, delete etc. to handle databases?

---

<div class="post-metadata">

**Author:** ![madhavi.bade](https://avatars.discourse-cdn.com/v4/letter/m/50afbb/32.png) [@madhavi.bade](https://community.automationedge.com/u/madhavi.bade)\
**Post date:** [March 20, 2020, 9:52am UTC](https://community.automationedge.com/t/sql-execute-script-plugin/1827/2 "2020-03-20T09:52:27Z")

</div>

‘Execute SQL script’ step can be used for all types of queries.  
However, because of the scripting/dynamic nature of the step, it does not use prepared statements and thus is not intended to work fast or optimal.  
For good performance we should use dedicated steps like Table Output (insert into), Table Input (Select), Update, Delete, etc.