58

Now we start moving from LCS to PPAC we also lose the possibilities to have SQL insight;

  • Long running queries
  • Current blocking tree
  • Current blocking statements
  • End SQL process
  • Live view (for current running queries)

Nice to have;

  • Index management (Overview of indexes and their capacity, deactivating of indexes, missing indexes).


Until now we were self facilitating in LCS when it came to SQL deadlocks or performance issues (most of the time). It will take to long when we have a deadlock in Production and we need to wait for support. It would be very inefficient if we need to create a support ticket to get the long running queries, running queries or missing indexes.

Category: General
STATUS DETAILS
New

Comments

M

It is very important to have control over ones own deployments when it comes to performance. Waiting for Microsoft tickets is unacceptable. Microsoft teams have preached that PPAC will have parity to LCS or they haven't done their job. It is no where near parity.....more like parody in that it's comical the lack of tools we have for F&O environments. App Insights is lacking and barely gives enough details without doing ones own custom telemetry.

Category: General

M

Why this is critical in PPACWhen moving from LCS to PPAC, we lose direct SQL insight that is essential for operating D365 F&O in production. Capabilities such as viewing long-running queries, blocking trees, live executing statements, and terminating problematic SQL sessions are required to resolve deadlocks and performance issues in real time.Without these, even basic production incidents would require opening Microsoft support tickets just to obtain transient runtime data. This significantly increases resolution time and business impact, especially since many SQL issues must be analyzed while they are happening.Today, partners and customers can self-service most SQL-related incidents in LCS. Removing this without an equivalent PPAC replacement is an operational regression and introduces unnecessary dependency, downtime risk, and inefficiency.At minimum, PPAC should provide read-only SQL runtime insight and index visibility to maintain current operational capabilities.

Category: General