Allocating system resources

It really depends on what Batch processes you are talking about. Its important to understand the Dynamics NAV version principle, to know what is happening at the server. Basically though committed transactions are being written to the disk, in the order that they were committed. This is happening through the commit cache. Of course whilst this is happening, you could have other processes reading data, they can read etiehr from commit cache normal cache or the Drives, so it matters only that the data has been committed.

For this reason, some precesses can be modified to share the server resources, some can't. A good example is the Batch Post invoices routine. This routine grabs a sales order or un-posted invoice, posts it, and then commits the data, then grabs the next order to post. After the commit, and before the next get, you can insert a wait, and whilst the client is waiting, other tasks can commit data.

But if you have a routine that needs to run from start to finish, and is writing data to the disk but can not commit till the end, then you can't really do too much. If you put a wait in there, you will allow other users read access to data, but others need to write, so it may not have any big advantages.

lubost wrote:

Topic can be marked as solved.

This is on you. You just needs to put the [SOLVED] prefix into first post subject... 8)

David Singleton wrote:

lubost wrote:

...
- do COMMITs (if they are possible) in appropriate places in program sequence.
...

And of course, use COMMIT only if you are absolutely 100% certain what you are doing.

Actually, only when you're 200%, absolutely, very very ... etc etc ... sure