Hi Guys,
We've got a nice resource, SaaS FAQ, on our web site. Thanks to Marketing and Support team!
It answers most of the questions about how do we provision services, how do we backup, where do we store, etc.
SaaS FAQ on Acumatica Web Site
Another thing, if you experience the service disruption, we have emergency channel to report for it via web portal here:
Service Outage Report
Finally, as our price list includes Service section, please do not hesitate to visit this page for Acumatica Provisioned Services
Services from Acumatica
We also have a document, explaining the DB growth depending on different modules transactions amount.
I would like to copy it here:
![]()
Please note, this report does not put into consideration amount of Entities, like for example Fixed Assets.
I am going to stress, number of entities is important only if its significant, say more than tens of thousands.
If we take Fixed Assets module, the size of the tables associated with Assets depends on
A. Asset Useful Life in Month.
B. Number of assets.
So if our assets are in average live for 5 years = 60 month, and we have 10,000 of assets. Then multiplication will tell the actual number of sizable records in the system = 600,000 historical records.
If we purchase 1,000 assets yearly. Add 60,000 historical records every year.
Based on real life example, each asset consumes around 50kB space in the DB. So to speak, 20,000 of assets will grow your database by 1 GB. Its a one time growth, but you need to account for it.
Other modules like Inventory or Accounts Receivable are not so sensitive to number of Entities, unless there is a really big number of them.
All the best,
Sergey.
We've got a nice resource, SaaS FAQ, on our web site. Thanks to Marketing and Support team!
It answers most of the questions about how do we provision services, how do we backup, where do we store, etc.
SaaS FAQ on Acumatica Web Site
Another thing, if you experience the service disruption, we have emergency channel to report for it via web portal here:
Service Outage Report
Finally, as our price list includes Service section, please do not hesitate to visit this page for Acumatica Provisioned Services
Services from Acumatica
We also have a document, explaining the DB growth depending on different modules transactions amount.
I would like to copy it here:
Please note, this report does not put into consideration amount of Entities, like for example Fixed Assets.
I am going to stress, number of entities is important only if its significant, say more than tens of thousands.
If we take Fixed Assets module, the size of the tables associated with Assets depends on
A. Asset Useful Life in Month.
B. Number of assets.
So if our assets are in average live for 5 years = 60 month, and we have 10,000 of assets. Then multiplication will tell the actual number of sizable records in the system = 600,000 historical records.
If we purchase 1,000 assets yearly. Add 60,000 historical records every year.
Based on real life example, each asset consumes around 50kB space in the DB. So to speak, 20,000 of assets will grow your database by 1 GB. Its a one time growth, but you need to account for it.
Other modules like Inventory or Accounts Receivable are not so sensitive to number of Entities, unless there is a really big number of them.
All the best,
Sergey.