Threadser.net
數據
關鍵字
功能建議
Blog
Following
Threads
Change language
登入
串文
串文鏈結
2025-03-15 04:34
SQL horror story: The query worked yesterday. The database didn’t change. The same query now takes 10 minutes. Nobody knows why.
讚
135
回覆
61
轉發
作者
Manish | Sql & Database Developer
rebellionrider
粉絲
1,566
串文
41+
讚
回覆
轉發
24小時粉絲增長
發文前
1,555
發文後24小時
1,566
變化
+11 (0.71%)
互動率
(讚 + 回覆 + 轉發) / 粉絲數
12.52%
回覆 (BETA)
最先回覆的內容
發文後
用戶
內容
5 小時內
Manish Pandey
mnk.qc
Different Transactions / read write lock
6 小時內
Dalibor Karlović
dkarlovi
Locks or Index had a cardinality change (got corrupted or even un-corrupted).
15 小時內
Sam
rapidowl
Were you running it on your own box and heat sink started coming away?
16 小時內
opentokix
opentokix
It’s because your tmp disk is full
17 小時內
Amedee Van Gasse
amedeevangasse
The other way around is even scarier.
19 小時內
Bob McCown
bob.mccown
This is me, last week.
19 小時內
Boyd Petrie
boydpetrie
Someone drop an index?
19 小時內
Paul Michael Rest
paulrusof
Your query broke something. Added a bunch of garbage rows or messed up the indexes or deleted stuff you weren’t expecting it to. The database definitely changed. Hopefully you have someone at your organization who can troubleshoot the query and figure out why (probably not that hard). In the meantime, hope you have regular backups to restore from. Next time deploy to a test environment first.
20 小時內
Sagaran Jos
sagaranjos
Most probably some other large update is happening on the table
21 小時內
correcthoarsebatterystaple
Have DOGE unplug their stuff.