Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Transaction table without locking issues
ronvdw
Member Posts: 16
In one of our solutions we use a transaction table which has the following layout:
Entry No. -> this field has been provided with the AutoIncrement property
Record ID
The purpose of this table is to register record id's at several NAV processes. This function may not block existing processes. The processing of these record id's is done in a separate process (Job Queue or a web service). Records are deleted from the transaction table after processing. Deleting these records, however, may place a lock on the table which prevents new records to be added.
Does anyone has a proper solution for this scenario?
Entry No. -> this field has been provided with the AutoIncrement property
Record ID
The purpose of this table is to register record id's at several NAV processes. This function may not block existing processes. The processing of these record id's is done in a separate process (Job Queue or a web service). Records are deleted from the transaction table after processing. Deleting these records, however, may place a lock on the table which prevents new records to be added.
Does anyone has a proper solution for this scenario?
Connectivity Studio for Microsoft Dynamics NAV - Where Microsoft Dynamics NAV meets the world
0
Comments
that's the only way to can control how sql decides to lock the records. But even then if you are running a serialized transaction (i.e. Posting) , SQL may decide to lock the whole table, or page, or index.
I have had a table with PK Batch No.,"entry no." Where Entry no was auto incremented and as long as there weren't any secondary indexes, sql didn' t lock two processes deleting and inserting concurrently.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n