Dealing with Record Locking issues with SQL
Posted on 2008-06-13
My company mainly works in the iSeries environment with RPG programs. In the RPG programs we have record level access of our files meaning when a record is read it is locked and cannot be accessed by another program trying to update it.
We have started to make the jump from RPG to C# and ASP.Net applications, still using the iSeries as the database. As far as I can tell there is no record locking when using SQL in these applications. I am using iDB2 for ADO.net for a connection to the iSeries.
Could someone please let me know how you handle record locking when using SQL? In specific, how do you keep two people from not trying to update the same record at the same time? I'm interested in ways to do this using both the iSeries and MS SQL server.