Timeline for Which kind of table design best suitable for normalization in SQL server?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 27, 2017 at 17:50 | comment | added | Vérace | Look on portfolio as a summary table (maybe a materialized view?). The fields pf_asset_value and pf_asset_reserve are never updated directly but instead come from the "subtables". Use a trigger, MV (or virtual) field - I'm not an expert on SQL Serverso I'm not sure of the best approach for that RDBMS. If you're not, perhaps a new question with a link back here (and a comment to let me know :-) ). | |
| Sep 27, 2017 at 17:40 | comment | added | RGS | Here portfolio table will act as main table i.e super table, and vehicle and gold tables will act as sub tables. Is my understanding correct? What is the purpose of pf_asset_value and pf_asset_reserve columns maintaining in Portfolio table because vehicle_reserve and gold_reserve columns have been already maintaining in Vehicle and Gold Tables respectively? | |
| Sep 27, 2017 at 1:33 | vote | accept | RGS | ||
| Sep 26, 2017 at 19:52 | history | edited | Vérace | CC BY-SA 3.0 |
deleted 35 characters in body
|
| Sep 26, 2017 at 19:44 | history | answered | Vérace | CC BY-SA 3.0 |