Timeline for Query sometimes take 25 seconds to run
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 22, 2020 at 8:29 | vote | accept | eugenekr | ||
| Jan 22, 2020 at 8:29 | answer | added | eugenekr | timeline score: 3 | |
| Jan 22, 2020 at 8:29 | history | edited | eugenekr | CC BY-SA 4.0 |
deleted 366 characters in body
|
| Jan 22, 2020 at 8:23 | history | edited | eugenekr | CC BY-SA 4.0 |
added 370 characters in body
|
| Jan 20, 2020 at 9:08 | history | edited | eugenekr | CC BY-SA 4.0 |
added 499 characters in body
|
| Jan 20, 2020 at 8:58 | comment | added | eugenekr | It is a simple query which always returns 3 rows and takes 200 ms, but the same query with the same parameters and returned data set sometimes starts taking almost exactly 25 seconds. | |
| Jan 18, 2020 at 19:30 | answer | added | David Browne - Microsoft | timeline score: 1 | |
| Jan 18, 2020 at 12:43 | comment | added | Martin Smith | Regarding the fixing itself do you have the "last good plan" auto tuning option enabled? | |
| Jan 18, 2020 at 9:20 | comment | added | Rob Farley | More info could be useful. Query plans, the query itself... | |
| Jan 18, 2020 at 9:20 | answer | added | Rob Farley | timeline score: 1 | |
| Jan 18, 2020 at 6:34 | history | asked | eugenekr | CC BY-SA 4.0 |