#BCALHelp - We are having a case where the invoicing takes to long time. The invoicing time can vary between 4-15h even though the invoices ~same. When it goes slow the VM and Azure SQL only has CPU workload 7-16% resp. 14-40% . Any ideas? Currently running on BC22. No users were present in system. - ThreadSky

About ThreadSky

navfreak.bsky.social • 86 days ago

#BCALHelp - We are having a case where the invoicing takes to long time. The invoicing time can vary between 4-15h even though the invoices ~same. When it goes slow the VM and Azure SQL only has CPU workload 7-16% resp. 14-40% .
Any ideas? Currently running on BC22.
No users were present in system.

Comments

schnieringer.bsky.social•86 days ago

Such an analysis from a distance is almost impossible. To analyze logging on the SQL server, there are other processes in BC that are automatically executed there. Are there processes such as backups etc. running on the SQL server or the BC server at the time... unfortunately a lot of possibilities.

phenno.bsky.social•86 days ago

I have to agree, such analysis is anything but simple to be done this way... Could be a number of reasons but I would start to dig/collect DMVs and other available data and compare slow and fast runs.

phenno.bsky.social•86 days ago

How do you mesaure workload on Azure SQL? Are you collecting/checking DMVs or something else? Is that managed SQL or simple Azure SQL Database?

navfreak.bsky.social•86 days ago

Nothing fancy, I just look at the CPU as an overall indicator and then in the query store.

navnab.com•86 days ago

We faced similar problem on onprem Sql Server. It turns out it was an IOPS issue with the tempdb drive. Check if you have similar things with Azure Sql and if there is a setup for IOPS... The IT guy talked about a 'burst' somewhere. Not sur what it means.
I hope it helps

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply