# Natural to SQL Record locking

**URL:** <https://techcommunity.softwareag.com/t/natural-to-sql-record-locking/75472>\
**Category:** Forum\
**Tags:** Adabas-Natural, Adabas, Adabas-Add-on-Products, SQL-Access, Mainframe-Integration, CONNX\
**Created:** [October 2, 2007, 2:10pm UTC](https://techcommunity.softwareag.com/t/natural-to-sql-record-locking/75472 "2007-10-02T14:10:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Axl](https://avatars.discourse-cdn.com/v4/letter/a/e8c25b/32.png) [@Axl](https://techcommunity.softwareag.com/u/Axl)\
**Post date:** [October 2, 2007, 2:10pm UTC](https://techcommunity.softwareag.com/t/natural-to-sql-record-locking/75472/1 "2007-10-02T14:10:46Z")

</div>

We are interfacing between Natural (Unix) and our Clients SQL databases on a constant basis.

How do I fugure out what type of locking occurs when I update the SQL table?

How do I make sure that only the Current record(s) being processed is locked (until committed)?

Is it possible that some setting within Entire Access is causing Table locking as opposed to record locking?

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 2:48pm UTC](https://techcommunity.softwareag.com/t/natural-to-sql-record-locking/75472/2 "2021-04-02T14:48:47Z")

</div>