Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • Its possible, but you really need the SQL Server wait data to do anything actionable that isn't as likely to cause more problems as fix it. The biggest thing you can do now is to put in systems to gather this data for when/if this happens again. Commented Mar 21 at 16:35
  • I'm not very familiar with SQL Server, but it seems unlikely that reads would block writes unless you are using something like select for update. If you have high volume inserts, that can cause contention with a lot of indexing strategies. Without more info we can only guess. Commented Mar 21 at 21:21
  • What type of transactions is configured? Commented Mar 22 at 7:36
  • 1
    In MSSQL big selects can and do lock entire table. Commented Mar 23 at 9:44
  • @freakish If true, that's pretty sub-par. Do you have a reference for this behavior? Commented Mar 25 at 14:49