To continue this, does anyone have any experience or opinion on time/performance in posting a GL batch with the following conditions?

2000 entries per batch

8 details per entry

5 optional fields per detail

500 batches per posting sequence (500 marked ready to post then post all)

Could there be a progressive deterioration in Sage business logic processing (not SQL) because of database size?  GLPOST has around 200 million records.

There very little business logic involved posting a batch, this is all a SQL problem, memory, disk array, etc..  Also, have you set your recovery models to Simple?

There very little business logic involved posting a batch, this is all a SQL problem, memory, disk array, etc..  Also, have you set your recovery models to Simple?

That's kind of reassuring.  I will continue to recommend they focus on SQL.  They might be using full recovery model with the intention to use it properly for potential recovery.  Whether they have implemented is another question.

We have hit at least one hard limit in Sage 300 (maximum posting sequence count of 9,999,999 for example) hence the thinking around the business logic.  I'm not aware (so far) of anyone handling this volume of data or database size with Sage 300.

Thanks again, Jay.