Share via

sys.dm_pdw_errors maximum rows

Taiob Ali 101 Reputation points MVP
2024-01-12T15:00:05.5533333+00:00

As per this document, sys.dm_pdw_errors can retain a maximum of 10,000 records. Why am I seeing only 3,200 in my environment?
Dedicated SQL Pool
Gen2: DW2000c

Azure SQL Database
0 comments No comments

2 answers

Sort by: Most helpful
  1. AnnuKumari-MSFT 34,571 Reputation points Microsoft Employee Moderator
    2024-02-01T10:49:53.1033333+00:00

    Hi Taiob Ali , Thankyou for using Microsoft Q&A platform and thanks for posting your query here. It seems that you are seeing only 3,200 records in your ded sql pool environment, while the documentation states that sys.dm_pdw_errors can retain a maximum of 10,000 records.

    Pausing compute causes the storage layer to detach from the Compute nodes. The compute resources are released from your account. You are not charged for compute while compute is paused. Resuming compute reattaches storage to the Compute nodes, and resumes charges for Compute. When you pause a dedicated SQL pool (formerly SQL DW), DMV counters are reset.

    For more details, kindly check this documentation: Pausing and resuming compute Hope it helps. Kindly accept the answer by clicking on Accept answer button. Thankyou

    Was this answer helpful?


  2. Sedat SALMAN 14,455 Reputation points MVP
    2024-01-13T00:35:00.1666667+00:00

    The count of rows in the DMVs, including sys.dm_pdw_errors, resets when a dedicated SQL pool is either paused or when its scale is changed. If your environment underwent such operations, this could explain the lower count of records

    Was this answer helpful?


Your answer

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