Timeline for Alternatives to running query for rarely changed data everytime on large table
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 8, 2018 at 19:37 | answer | added | Joe Obbish | timeline score: 1 | |
| Apr 6, 2018 at 17:09 | answer | added | Elise van Looij | timeline score: 0 | |
| Apr 6, 2018 at 16:58 | answer | added | Doug | timeline score: 0 | |
| Apr 6, 2018 at 7:16 | vote | accept | JaggenSWE | ||
| Apr 6, 2018 at 3:44 | answer | added | Vladimir Baranov | timeline score: 9 | |
| Apr 5, 2018 at 21:14 | answer | added | Doug | timeline score: 1 | |
| Apr 5, 2018 at 17:57 | comment | added | DForck42 | yeah it honestly sounds like there's a need to normalize this data | |
| Apr 5, 2018 at 16:53 | comment | added | paparazzo | Can you post the definition for the table? What is the nature of the table that it has so many entries? | |
| Apr 5, 2018 at 15:11 | history | tweeted | twitter.com/StackDBAs/status/981912331809673216 | ||
| Apr 5, 2018 at 14:39 | history | edited | MDCCL |
Added the generic tag of the database management system of relevance.
|
|
| Apr 5, 2018 at 14:29 | answer | added | Flourid | timeline score: 3 | |
| Apr 5, 2018 at 14:26 | answer | added | RBarryYoung | timeline score: 11 | |
| Apr 5, 2018 at 14:20 | comment | added | RBarryYoung |
In myy experience, using DISTINCT <column> in a regular production query is almost always a sign that you are not normalized properly. If this is an OLAP database (i.e., not OLTP), then that can be OK, and you just need an index on PortName.
|
|
| Apr 5, 2018 at 14:15 | answer | added | Aaron Bertrand | timeline score: 10 | |
| Apr 5, 2018 at 14:00 | history | asked | JaggenSWE | CC BY-SA 3.0 |