I can't get diagnostics logging working on a dedicated sql pool

Ellen Heijmans 21 Reputation points
2025-01-15T08:25:39.6566667+00:00

I want to see the exec requests and waits on a dedicated pool.

So I created a log analytics workspace in the same workspace as the sql pool and I went to the dedicated sql pool and in the Diagnostics Settings option I created a new one for the logs exec requests and waits.

Then I connected to the database by using SSMS and ran a few queries.

But I can nowhere find the results. I don't see tables under Logs in the Log Analytics Workspace. I don't see them in the logs of the Synapse Workspace. There aren't any tables under the option Logs of the dedicated SQL Pool. And when I go to the Synapse Studio and look under Monitor to SQL Requests, that is empty too.

What am I doing wrong?

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
5,149 questions
{count} votes

Accepted answer
  1. Chandra Boorla 7,260 Reputation points Microsoft Vendor
    2025-01-20T17:48:41.3633333+00:00

    @Ellen Heijmans

    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).

    User's image User's image

    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.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Ellen Heijmans 21 Reputation points
    2025-01-20T08:04:28.6633333+00:00

    Hi Chandra. One of the things you mentioned was about time delay. That I have to check. But since I have to remove everything at the end of the day otherwise my 100,00 free Azure are gone in notime, I still have to try this out.

    Permissions - I've created the workspace and the SQL Pool. So I permissions to read the log should be in place.

    Diagnostic Settings - in my screenshots you can see that I've done this.

    Querying Logs - That's the problem: there aren't any.

    Log Analytics Workspace - Did that.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.