# How to serialise and store Relationnal "Star model " database i **URL:** \ **Category:** Elasticsearch\ **Created:** [April 4, 2019, 9:07am UTC](https://discuss.elastic.co/t/how-to-serialise-and-store-relationnal-star-model-database-i/175359 "2019-04-04T09:07:02Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![BENMOHAMED\_Abdelkade](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benmohamed_abdelkade/32/43473_2.png) [@BENMOHAMED\_Abdelkade](https://discuss.elastic.co/u/BENMOHAMED_Abdelkade)\ **Post date:** [April 4, 2019, 9:07am UTC](https://discuss.elastic.co/t/how-to-serialise-and-store-relationnal-star-model-database-i/175359/1 "2019-04-04T09:07:02Z")
Hello everybody hope you're doing great, i'm a total NooB at elastic-Search and i researched on the internet how to store highly related table with elastic search but it's quite confusing, here's my problem, I have Approximately 16 Tables (one fact table and the other are dimensions tables), i could do a SQL request where i join all the table in an array of long rows containing all the fields and mapping it in a tree way, but there will be tons of duplicated fields, For exemple the dimension table A " contain 3 persons: p1,p2,p3" and a Fact Table contain more than 1000 row (for examples) and all these row have foreign keys/references to these 3 persons, So what's the ideal way to store it? putting each table in a different Index or category or to embed everything in one single object per row ? Thanks in advance ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 2, 2019, 9:07am UTC](https://discuss.elastic.co/t/how-to-serialise-and-store-relationnal-star-model-database-i/175359/2 "2019-05-02T09:07:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.