# Es sync with sqlserver **URL:** \ **Category:** Elasticsearch\ **Created:** [September 29, 2016, 5:46am UTC](https://discuss.elastic.co/t/es-sync-with-sqlserver/61769 "2016-09-29T05:46:43Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![sergio\_imperato](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@sergio\_imperato](https://discuss.elastic.co/u/sergio_imperato)\ **Post date:** [September 29, 2016, 5:46am UTC](https://discuss.elastic.co/t/es-sync-with-sqlserver/61769/1 "2016-09-29T05:46:43Z")
hi, I have no experience in this area, but I have a classic requirement to synchronize a sql server with elastic search databases to speed up searches. I should evaluate two strategies: the first to keep the data updated in real time to contemplate the other one scheduled update per day. schematically you might mention some of the components that come into play for the two scenarios? And in the second case what is the processing load for the db we are talking about a hundred million occurrences? thanks to the availability that you can pay to my request for information. regards ---
**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:** [September 29, 2016, 6:13am UTC](https://discuss.elastic.co/t/es-sync-with-sqlserver/61769/2 "2016-09-29T06:13:29Z")
You can read that: [http://david.pilato.fr/blog/2015/05/09/advanced-search-for-your-legacy-application/](http://david.pilato.fr/blog/2015/05/09/advanced-search-for-your-legacy-application/) It represents my opinion on this. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:16pm UTC](https://discuss.elastic.co/t/es-sync-with-sqlserver/61769/3 "2017-07-05T22:16:17Z")