# Complete MySQL database to Elasticsearch

**URL:** <https://discuss.elastic.co/t/complete-mysql-database-to-elasticsearch/142266>\
**Category:** Elasticsearch\
**Created:** [July 31, 2018, 2:30am UTC](https://discuss.elastic.co/t/complete-mysql-database-to-elasticsearch/142266 "2018-07-31T02:30:58Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![nandan\_bigdata](https://avatars.discourse-cdn.com/v4/letter/n/f07891/32.png) [@nandan\_bigdata](https://discuss.elastic.co/u/nandan_bigdata)\
**Post date:** [July 31, 2018, 2:30am UTC](https://discuss.elastic.co/t/complete-mysql-database-to-elasticsearch/142266/1 "2018-07-31T02:30:58Z")

</div>

Hi Team,  
I am working on a data analysis project on MySQL Database which contains around 100 tables.

> Details are as below:-  
> Database Type :- RDBMS - MySQL  
> Total No. of Tables:- 100  
> The total Data size of Current MySQL Database:- 600 GB  
> Maximum number of columns in the table:- 12 Billion in Product Sales Table

I want to index my MySQL to Elasticseach where I can use Kibana for Data Visualization as well as Data Analysis platform where I can able to do report / Chart generation too.

Please tell me how to index all 100 MySQL tables to Elasticsearch to make sure everything should be work perfect as well as please let me know other scenarios where I have to take cautions.

Thanks,

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 31, 2018, 3:07am UTC](https://discuss.elastic.co/t/complete-mysql-database-to-elasticsearch/142266/2 "2018-07-31T03:07:51Z")

</div>

You're asking quite a lot here, basically for us to architect an entire project for you. We're happy to help with things, but I think this might be a bit much.

Have you considered engaging an organisation that can help?

---

<div class="post-metadata">

**Author:** ![nandan\_bigdata](https://avatars.discourse-cdn.com/v4/letter/n/f07891/32.png) [@nandan\_bigdata](https://discuss.elastic.co/u/nandan_bigdata)\
**Post date:** [July 31, 2018, 3:11am UTC](https://discuss.elastic.co/t/complete-mysql-database-to-elasticsearch/142266/3 "2018-07-31T03:11:01Z")

</div>

If my question is bothering you then I will drop it from here.  
Thanks for your earlier notice.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 31, 2018, 9:20am UTC](https://discuss.elastic.co/t/complete-mysql-database-to-elasticsearch/142266/4 "2018-07-31T09:20:14Z")

</div>

I don't think you are bothering anyone here and @warkolm's answer is accurate.  
We are happy to help on any specific question you might have but we can't really answer a so generic one which is basically "how do I move from a relational model to a document oriented model?" and "how do I move from a datastore to a search engine?".

One silly answer would be: just index each table as a new index. But you will see that does not work well with the search engine and document oriented paradigm.

So, you have to ask yourself some questions that I covered at: [Which is the best way to index the data from relational database](https://discuss.elastic.co/t/which-is-the-best-way-to-index-the-data-from-relational-database/141870/2)

Then, when you know more about your use case, features, data model, etc. we can help about sizing and other stuff. Feel free to ask.

---

<div class="post-metadata">

**Author:** ![nandan\_bigdata](https://avatars.discourse-cdn.com/v4/letter/n/f07891/32.png) [@nandan\_bigdata](https://discuss.elastic.co/u/nandan_bigdata)\
**Post date:** [July 31, 2018, 9:35am UTC](https://discuss.elastic.co/t/complete-mysql-database-to-elasticsearch/142266/5 "2018-07-31T09:35:16Z")

</div>

Yes I am agree. May be the way I express my question projected wrong meaning, but My motto was to just get the idea about how to handle MYSQL DB relationship in ES to make sure Analysis should be work perfectly.

Even I am working from my side. Hope Will find some solution then will update here..

Happy together learning. 😀😊

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 28, 2018, 9:35am UTC](https://discuss.elastic.co/t/complete-mysql-database-to-elasticsearch/142266/6 "2018-08-28T09:35:31Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
