Timeline for Should we add extra 5 columns or build a separate table?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 4, 2012 at 5:18 | comment | added | newbie14 | yes we already have a table called device in place which keep the details of the device eg. deviceID, deviceSerialNumber etc. | |
| Jul 2, 2012 at 16:15 | comment | added | Jon Seigel | @newbie14: In the case of device type and device serial, normalization would pull those two fields plus a new primary key column into a new table, probably called Device or Devices, and then you would put a DeviceId column in the main table. As far as system impact goes (performance or otherwise), it depends on the items I listed in my answer. In this case, though, normalization would make the fact table narrower/smaller, which is almost always a good thing. | |
| Jul 2, 2012 at 14:52 | comment | added | newbie14 | I appreciate your long list of information. So as I have listed earlier all mostly related for e.g. latitude,longitude,speed,date time,device type,device serial. So what is your idea of normalisation then we will end up with another problem of join? How to weight between to use join or not? | |
| Jul 1, 2012 at 13:50 | history | answered | Jon Seigel | CC BY-SA 3.0 |