RossW

My feedback

  1. 43 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  18 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    RossW commented  · 
    An error occurred while saving the comment
    RossW commented  · 

    Seems to be fixed in SQL Server 2017 CU10.

    RossW supported this idea  · 
    An error occurred while saving the comment
    RossW commented  · 

    I am experiencing this in SQL Server 2017 CU7. I sometimes have as many as 100,000+ entries in the errrolog per hour.

    Messages are often 10 milliseconds apart.

    It is 100% recoverable and ignorable.

    At least give us a trace flag to disable logging, or configure the timeout. I suspect the timeout is pretty short due to 10 ms between log entries and my monitoring often not reporting blocking beyond 30 seconds.

Feedback and Knowledge Base