Sage 100

Has anyone found a ceiling for how many transactions Sage 100 can handle? I know at some point it starts to slow down and the lookups get painful but is there a point where it will actually just give up and start throwing errors? We have a client that wants to do 3 million Sales Order lines in a year.

If they have heavy transaction volume, at the very least put them on SQL. Indexing abilities on that will help. Also, use some sort of the terminal server/cloud system to minimize issues with internal networks.

I don't think there is a limit at least not in non-SQL version. I have a client that has been running Sage 100 (non-SQL) for at least 10 years. Their sales volume is similar to what you describe. They crank out an average of 100 shipments per day and a typical shipment is 75-100 line items per order. Legacy modules (work order, Payroll and Job Cost) have a limit of 1 million records in a the old indexed tables but the 4x modules seem to handle large volume just slows some things down as you describe.

If there are 200 working days per year then 3M transactions per year is 15,000 transactions per day. I have a Sage 100 Premium customer that regularly processed orders that have 500+ line items. They are probably in the same range of transactions per year as you describe. I believe a more important consideration is how many line items per order. Entering a sales order in shipping data entry that has hundreds of lines uses a lot of memory. If you have more than a couple of hundred lines per order you need to have a lot of memory on the server (for advanced or premium as they use server-side processing). I believe my client has 128Gb of memory on the server.

Thanks everyone for this feedback!