Timeline for Single table with more columns vs multiple tables with fewer columns
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2020 at 9:05 | history | edited | CommunityBot |
Commonmark migration
|
|
| Feb 22, 2016 at 14:49 | answer | added | Ian_H | timeline score: 2 | |
| Feb 11, 2016 at 9:56 | answer | added | Dipa | timeline score: -3 | |
| Feb 2, 2016 at 6:48 | comment | added | Vincent Dagpin | Using execution plan is really a big help. It tells you what is the problem with your query. Ps: dont do loop, if possible use bulk processing, that feature is there already, use it | |
| Feb 2, 2016 at 6:46 | comment | added | Vincent Dagpin | For me, few columns more rows. It is easy to manage a portion by portion than having a large dataset. If your big concern is the large data in the future, dont. Sql server is designed with that kind of problem, all you have to do is design it properly. Having a large dataset is not a problem if you know how to optimize your query | |
| Feb 2, 2016 at 6:36 | history | edited | Paul White♦ | CC BY-SA 3.0 |
added 55 characters in body; edited title
|
| Aug 27, 2015 at 23:07 | history | tweeted | twitter.com/#!/StackDBAs/status/637038665529696256 | ||
| S Jul 1, 2015 at 4:04 | history | suggested | oNare | CC BY-SA 3.0 |
improving formatting
|
| Jul 1, 2015 at 3:42 | review | Suggested edits | |||
| S Jul 1, 2015 at 4:04 | |||||
| Jun 24, 2015 at 6:02 | review | First posts | |||
| Jun 24, 2015 at 6:24 | |||||
| Jun 24, 2015 at 5:58 | history | asked | Siddharth Patel | CC BY-SA 3.0 |