Mobile Log In
       Building and Delivering
Quality Software Results






Microsoft SQL Server picture (for illustrative purposes only)


DB2 for IBM i picture (for illustrative purposes only)


other databases illustration


database performance illustration via IBM Navigator for i


Solving the Biggest Challenges
Using Transaction Construct & SQL
  • Mission Critical / Industrial Strength Power and Scalability
  • for those SQL update processes active for multiple users and requiring the highest level of accuracy
  • simplify concurrency considerations
  • by explicitly locking rows (pessimistic row locking)
  • by preventing overlays (optimistic row locking)

  • Solve classic problems in a straight-forward manner
  • when inventory levels or detection of stock-out conditions need to be real time accurate
  • inventory quantity allocation at order entry time
  • pick/pack sheet print
  • when it is costly to POS sell more than you have
  • processes involving large numbers of order line updates and order header status changes
  • next unique invoice number assignment

  • Solve intermittant problems such as inconsistent run times or halts in processes
  • Could row locking decisions made behind the scenes by your database management software be the culprit?
  • proactively control which records are locked and which can be read by other update processes
  • Let us tell you about this technique to help you get into tune with more of these facets
  • Nail down row locking with our technique and gain these benefits
  • attempt lock for update for all files before initiating transaction reduces rollback situations (when updates to 2nd or 3rd file in line cannot be completed) (pessimistic row locking)
  • eliminate ability or need for other transactions to read uncommitted data or interim transaction results (dirty reads) and vice-versa

  • Technique does not Preclude Use of DB Contraints & Rules
  • use when a two-phase or two-pass approach is needed
  • use in high volume situations where overlays are occurring
  • use for types of updates where frequent rollback is costly and/or inefficient

  • Access MS SQL Server or IBM DB2 for i
  • from c# or VB.NET or 3rd Party .NET Languages

  • Technique
  • Note: Use of this transaction technique from c#, VB.NET or Visual RPG for .NET allows commit and rollback boundaries to span accross multiple stored procedure calls and SQL statements

  • Connect
  • Start Transaction
  • MS SQL Server Database Example:
  • using System.Data.SqlClient;

  • System.Data.SqlClient.SqlTransaction sqltxEnvironmentMasterRowUpdate = null;

  • sqltxEnvironmentMasterRowUpdate = cnnsvcMSSQL.BeginTransaction();

  • DB2 for i Database Example:
  • using IBM.Data.DB2.iSeries;

  • IBM.Data.DB2.iSeries.iDB2Transaction sqltxDigitalAssetDeliveryUIEventRowUpdate = null;

  • sqltxDigitalAssetDeliveryUIEventRowUpdate = cnnsvcDB2iSQL.BeginTransaction();

  • Prevent Interim Result Overlays - Access Data & Hold Pessimistic Row Lock(s)
  • Verify No Data Overlay Conditions (otherwise message user and rollback)
  • Start Update(s)
  • Commit if Successful, Otherwise Rollback
  • Dispose and Disconnect




  • Let us help you write these type of transactions
  • we can work with you to formulate a version of this technique for you based on your in-house standards





        go to the home page Top of Application Software     go to next series page     Site Map     Mobile View
You are at the web site of Tegratecs Development Corp.  Click here to go to the home page of this site...
Integrity, Integration and ROI from Your Software
Our contact information:
Tegratecs Development Corp.
1320 Tower Road
Schaumburg, IL 60173
847-397-0088
( please register or sign-in )
© 2017 Tegratecs Development Corp.