Skip to main content

SQL Server Timeouts–Find possible (dead)locks

Today it was all hands on deck, as one our production services started to scream error messages.

After checking the log telemetry and running some tests, we could pinpoint the issue to a database timeout. Read operations were executed succesfully but all right operations timed out.

This made us think that a deadlock was causing the issue. But how do you know for sure?

Read on how you can check this…

  • Open SQL Server Management Studio
  • Connect to the suspicious database
  • Right click on the database, select Reports and choose the Resource Locking Statistics by Objects report

I didn’t create a screenshot at the moment of the issue(too busy fixing it), but the report showed multiple sessions to the same table where one session was Granted a lock while the other where waiting.

To free the lock, you could kill the session using the session id that is causing the lock:

KILL <sessionid>

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.