You’re offline. This is a read only version of the page.
Announcements
26
We have a high volume of sales orders, production orders in our current system and we are planning to go live with BC Public Cloud in 1 month. Is there anyway we can avoid any performance issues with MS Azure Cloud prior to going live so we can prepare for high volume transactions?
Thanks
Nirav S.
I think your biggest concern when it comes to performance should be customized code that might not be optimal.
Microsoft will constantly monitor the load on your system and scale up / scale out as needed.
Table locking can also be an issue if you do a lot of posting during peak hours.
So it might be a good idea to queue some posting processes to off peak hours if possible.
Keep a close dialogue with your partner if you experience any issues so they can raise support tickets with Microsoft if needed.
It would be highly appreciated to hear about your experiences after you go live either here or in direct message.
Hi, You can check out the official Microsoft documentation below.
And, you can use the In-client performance profiler to check your running performance issues.
PS: This is the data provided by Microsoft last year, hoping to give you some reference.
Thanks.
ZHU
You will need both of those, in equal proportions
1. Automated Testing is available in BC but it may require some Azure Infrastructure too, not 100% sure about it but it is possible www.youtube.com/watch
2. Manual Testing: You will need to ensure that you have a handful of BC Functional Consultants or specific BC QA Personnel, who know Business Central quite well. Explain them the scenarios and how your integrations/customizations will work, they'll help you get it manual load tested and may even assist ironing out bugs which can hamper systems
Hi There - Your question is quite interesting. OOTB BC is generally built to handle large number of transactions as it has got enough juice from Azure to be able to handle SaaS workloads. However there are no settings as such which will determine how many transactions can BC handle, so you can't really check/tweak anything before you go-live
However, if issues happen with OOTB BC, you can surely report to Microsoft
Also,
1. Do you have customizations deployed in your brand new BC Cloud Instance which will work post go-live?
2. Will your BC environment be integrated with any 3rd party website for fetching/sending data (3PL/4PL, etc.)?
The above two factors will largely determine how BC responds to large volume of transactions. The extensions deployed should be thoroughly load tested with proper QA and same should happen for your integrations. Loosely tested integrations/customizations can prove to be a headache. Make sure you deploy enough man-power now to test, than to worry later
Some other pointers to take into consideration:
1. Ensure there's no garbage data in masters (Often, there are blank rows of master data created, delete them)
2. Ensure you have your Job Queues scheduled at times when users aren't working (like the posting batch jobs)
3. Get rid of redundant data (If you have 3 customers named Google Inc, evaluate why you need 3 customers of the same name). Same goes for vendors. This will significantly improve your search results in SO/PO. Make sure to nomenclature your master data appropriately for search results to work faster
4. Deploy/Use telemetry in BC to be able to monitor workloads for a day/month to analyze where things go pretty bad and fix before London bridge collapses
#1
André Arnaud de Cal...
294,206
Super User 2025 Season 1
#2
Martin Dráb
232,968
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
