Comments
3 comments
-
This is a old post but we are also experiencing this as a indication today 15 times
Medium 24 Aug 2020 at 12:41 Medium 24 Aug 2020 at 12:15 Medium 24 Aug 2020 at 12:10 Medium 24 Aug 2020 at 12:10 Medium 24 Aug 2020 at 11:40 Medium 24 Aug 2020 at 11:37 Medium 24 Aug 2020 at 11:01 Medium 24 Aug 2020 at 10:07 Medium 24 Aug 2020 at 09:35 Medium 24 Aug 2020 at 09:28 Medium 24 Aug 2020 at 08:30 Medium 24 Aug 2020 at 08:20 Medium 24 Aug 2020 at 08:09 Medium 24 Aug 2020 at 08:01 Medium 24 Aug 2020 at 04:44 without having to filter out alerts are there any other options -
Has anyone found a solution to this? We've recently opened up monitor to other users and are encountering the same issue.
-
Sorry, I thought I updated this previously but it looks like that's not the case. We asked our developers to uncheck the "Indicate changed objects in the Object Exporer and update indicators every n seconds" setting in the SQL Source Control options and that seemed to help. It's more of a workaround than a solution.
Obviously, with Source Control not polling for changes, the developers need to manually check more frequently so they know what's been modified by others.
Add comment
Please sign in to leave a comment.
Example:
Deadlock victim
<frame procname="tempdb.dbo.RG_WhatsChanged_v4" line="275" stmtstart="24182" stmtend="25836">
Deadlock winner