Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
We're looking into setting up SLAs and KPIs for all our cases. We are creating roughly 350 cases on a daily basis. I'm just looking for some suggestions and ideas on what to potentially expect with the performance caused by all those wait conditions. the max wait would be 2 hours. Should i look into alternate solutions?
SLAs and KPIs behind the scene use the waiting workflow sort of features in CRM. If your SLAs are not that complicated, if they will only have few SLA items, 350 cases a day should not affect the performance of your CRM that much. As long as you do regular maintenance to cleanup data from tables like AsyncOp, it should be fine. And your CRM server / SQL Servers should also have reasonable resources allocated - mainly disk pace, mem and CPU.
If you are creating SLAs, better to spend some time looking into best practices of creating and maintaining SLAs. The following links will be handy and you could google and find more sources to know more about SLAs.
See current specs and statictic of the SQL server.
Its a dedicated (VM) SQL server for this Dynamics org (meaning, the SQL server is hosting a single database). The Database size is 200Gb. The VM has 100Gb Ram, 87Gb used for SQL.
Disk Usage and Table size
Business Applications communities