Question
You are migrating SAP to Azure. The ASCS application servers are in one Azure zone, and the SAP database server is in a different Azure zone. ASCS/ERS is configured for high availability.
During performance testing, you discover increased response times in Azure, even though the Azure environment has better compute and memory configurations than the on-premises environment.
During the initial analysis, you discover an increased wait time for Enqueue.
What are three possible causes of the increased wait time? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
- A. a missing Enqueue profile
- B. disk I/O during Enqueue backup operations Correct
- C. misconfigured load balancer rules and health check probes for Enqueue and ASCS
- D. active Enqueue replication Correct
- E. network latency between the database server and the SAP application servers Correct
Explanation
Enqueue wait time grows when the lock operations themselves take longer: disk I/O while the enqueue table is backed up, the synchronous replication of every lock to the Enqueue Replication Server, and the round trips across zones between the application servers and the database all add latency to each lock request. A missing Enqueue profile would stop the enqueue server from starting rather than slow it down. Misconfigured load balancer rules or health probes break connectivity or failover to ASCS instead of producing a measurable increase in wait time.
