# Indexing data from Oracle database tables

**URL:** https://discuss.elastic.co/t/indexing-data-from-oracle-database-tables/17870
**Category:** Elasticsearch
**Created:** [June 3, 2014, 3:29am UTC](https://discuss.elastic.co/t/indexing-data-from-oracle-database-tables/17870 "2014-06-03T03:29:29Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Praison\_Selvaraj](https://avatars.discourse-cdn.com/v4/letter/p/278dde/32.png) [@Praison\_Selvaraj](https://discuss.elastic.co/u/Praison_Selvaraj)
#### Post date: [June 3, 2014, 3:29am UTC](https://discuss.elastic.co/t/indexing-data-from-oracle-database-tables/17870/1 "2014-06-03T03:29:29Z")

</div>

What is the suggested approach to index records from tables in Oracle  
database?

We are considering indexing the data just when the user logs in so that the  
data is available for search and do away with the index when the user  
session expires or logs out. We need to do this for around 15 tables (upto  
5000 records per table for a user) per user and this is to be done for the  
90K users when the log in.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1292d1ab-2449-43ae-86e9-9295539ad86c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1292d1ab-2449-43ae-86e9-9295539ad86c%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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: [July 6, 2017, 1:25am UTC](https://discuss.elastic.co/t/indexing-data-from-oracle-database-tables/17870/2 "2017-07-06T01:25:07Z")

</div>


