Timeline for Optimization of a query to retrieve records randomly with multiple joins and filters
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 19, 2022 at 15:00 | history | tweeted | twitter.com/StackDBAs/status/1582748411446845440 | ||
| May 10, 2020 at 3:40 | vote | accept | Adolfo F. Ibarra Landeo | ||
| May 7, 2020 at 12:42 | answer | added | Josh Darnell | timeline score: 5 | |
| May 7, 2020 at 3:54 | comment | added | Adolfo F. Ibarra Landeo | @JoshDarnell thanks. It’s done. I don’t know if that’s the case. I’ll try to upgrade that tomorrow cause I don’t have access from my home. But it does not seems to be related to the query itself? I mean, it’s not too heavy by itself? Also, I have to say that the application is in a dev environment right now, no more than 5 concurrent users in a single point of the day. 15 seconds for a single call is too long. | |
| May 7, 2020 at 3:52 | history | edited | Adolfo F. Ibarra Landeo | CC BY-SA 4.0 |
added 82 characters in body
|
| May 7, 2020 at 3:32 | comment | added | Josh Darnell | Hi, Adolfo! Could edit your question to include the service tier of Azure SQL Database you're using? The numbers in that execution plan indicate that your queries are being throttled pretty heavily in terms of CPU. | |
| May 7, 2020 at 2:49 | review | First posts | |||
| May 7, 2020 at 9:23 | |||||
| May 7, 2020 at 2:42 | history | asked | Adolfo F. Ibarra Landeo | CC BY-SA 4.0 |