It sounds like you've diligently checked the common causes. Since you're not seeing any logs at all, even after waiting and confirming the setup, here are a few additional points to consider and test:
Resource Provider Registration - This is often overlooked. Ensure the Microsoft.Synapse resource provider is registered in your Azure subscription. You can check this in the Azure portal by going to Subscriptions -> Your Subscription -> Resource providers. Search for Microsoft.Synapse. If the status is NotRegistered, click Register. This is crucial for proper integration.
Do the same for Microsoft.OperationalInsights (needed for Log Analytics).
Log Analytics Workspace Location - While it's good practice to keep resources in the same region, double-check that the Log Analytics workspace is in a region that supports diagnostic logging for Synapse Dedicated SQL Pools. Although rare, regional limitations can exist.
Diagnostic Setting Scope - Confirm that the diagnostic setting is applied at the correct scope. It should be applied to the dedicated SQL pool resource itself, not the Synapse workspace or a higher-level resource group.
Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Thank you.