https://www.aras.com/community/f/development/3881/sql-procedures-vs-applysql---what-s-less-not-recommendedHi, &quot;AML first&quot; is probably on of the most important things to consider when developing custom code in Aras. And luckily most of all use cases can be covered with AML. But sometimes things have to be done with SQL. I wonder if there is a benefit whenja-JPTelligent Community 12https://www.aras.com/community/thread/1965?ContentTypeID=1Wed, 15 Aug 2018 11:27:27 GMT916d3f7e-8ddc-42f8-8d45-380822f51406:0bf8cde6-f5fb-4b0f-988f-2d2c19b9487dEli DonahueHi Angela, If you absolutely have to use SQL for a task (like minor_rev, as you mentioned), then creating a SQL item in the Aras database is probably the best way to go. You can reuse the same SQL across methods, maintain the SQL in one place, and you can package it up like any other method or configuration item. A word of caution - not just for you, but also anyone else who finds this thread - modifying Aras data via direct SQL can have unintended consequences such as data corruption, data loss, or bypassing the permission model. It should be used only when there is no other option, and it should be tested extensively in dev/test environments before releasing to production. As you mentioned, AML and IOM are the preferred approaches for retrieving and modifying Aras data. Eli <hr /> Eli Donahue Aras Labs Software Engineer<div style="clear:both;"></div>