Timeline for Certain SO profile pages won't load ("Oops! Something Bad Happened!")
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 16, 2018 at 6:39 | comment | added | T.J. Crowder | Working great this morning, thanks! | |
| Jul 16, 2018 at 6:34 | vote | accept | T.J. Crowder | ||
| Jul 16, 2018 at 6:34 | history | edited | T.J. Crowder | CC BY-SA 4.0 |
fix a couple of typos
|
| Jul 15, 2018 at 15:23 | comment | added | Taryn StaffMod | @ShadowWizard it’s possible that would happen. Since it’s the weekend I didn’t dig in too much on this. My goal was to get the page to load for the time being, I’ll look closer next week. The hope would be that since we sync things via availability groups, the query store selections would sync as well but I’ll have to look later. | |
| Jul 15, 2018 at 15:19 | comment | added | Shadow Wizard | From the little I understood it means that when you'll "fail the database over to a different server" again, it might pick the wrong plan again (since you forced it only on the current server) and this bug will just happen again. Is this correct? If so, why not just get rid of the bad execution plan so it can't be picked up in the future? | |
| Jul 15, 2018 at 15:03 | history | answered | TarynStaffMod | CC BY-SA 4.0 |