Synapse Dedicated pool Scalling up issue

Hey Samir Kohli,

I see you're facing a scaling issue with your Synapse Dedicated pool after increasing the DWUs from 300 to 400. It's been 6 hours, and it seems like the change hasn't taken effect yet. Here are a few steps you can take to troubleshoot the issue:

Check the Status: First, verify the status of your dedicated SQL pool. Sometimes, scaling operations can take longer than expected. You can do this through the Azure portal, PowerShell, or T-SQL. Confirm that the scaling process is still underway or if it has encountered an issue.

Existing Transactions: Remember that scaling requires the system to kill all incoming queries and roll back any existing transactions for a clean state. If there were long-running operations or numerous transactions at the time of your scaling request, that could contribute to delays.

Monitor Resource Utilization: Use the monitoring tools available in Azure Synapse Analytics to check if there are any concurrent query limits or resource utilization issues that may be impacting performance.

Known Issues: It's also a good idea to review the known issues for Azure Synapse Analytics to see if there are any outages or problems that could be affecting scaling operations.

Retry the Operation: If you find that your pool is not scaling and you're not able to determine the cause, you might want to try scaling it once again or lowering the DWU temporarily and then increasing it back to see if that resolves the issue.

If you're still having trouble after these steps, creating a support ticket might be a good option.

Reference Documentation:

• Azure Synapse Analytics Dedicated SQL Pool - Scale
• Scaling Operations
• Monitor SQL Pool State
• Known Issues in Azure Synapse Analytics

Hope this helps! Let me know if you have any other questions or need further assistance.

Thanks!

Kalyani