Does the commit cache property has any significance on the SQL Server option ver 3.70 ? What effect would adding frequent COMMIT statements have if we are using SQL Server option (espicially if we are running a long batch job) ? Are there any special guidelines or tips when implementing big batch jobs on Navision SQL (like batch posting of 100 Transfer Orders etc…) ? Any tips/help on this will be appreciated. Kmbhartiya
The Commit Cache setting is for Navision Server only and has no effect on the SQL option. The effect of frequent COMMIT statements is to make transactions shorter, which is always ideal because locks are held for shorter periods and concurrency is improved over having longer transactions. One down side is that Navision keeps many client-side caches (records, SIFT sums, SQL statement handles, BLOBs etc), some of which cannot persit across transactions, causing re-reads. Another issue is that you as a programmer need to ensure data consistency between your transactions, which can be tricky if the tasks are not isolated. Transactions handle this for you. However sticking to the goal of keeping transactions as short as possible is beneficial on any database system. Just by-the-way, you might like to consider getting hold of Update1 for 3.70B (i.e. the first update issued after the 3.70B service pack) which solves a nasty issue with transactions remaining open (thereby holding locks) while message boxes are being displayed, if you have this situation in your code. See item 1 in http://www.mbsonline.org/forum/topic.asp?TOPIC_ID=12967