# Ingesting Data using Agent (SQL Input Integration)

**URL:** <https://discuss.elastic.co/t/ingesting-data-using-agent-sql-input-integration/340820>\
**Category:** Elastic Agent\
**Created:** [August 15, 2023, 8:58am UTC](https://discuss.elastic.co/t/ingesting-data-using-agent-sql-input-integration/340820 "2023-08-15T08:58:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ksaimohan2k](https://avatars.discourse-cdn.com/v4/letter/k/f4b2a3/32.png) [@ksaimohan2k](https://discuss.elastic.co/u/ksaimohan2k)\
**Post date:** [August 15, 2023, 8:58am UTC](https://discuss.elastic.co/t/ingesting-data-using-agent-sql-input-integration/340820/1 "2023-08-15T08:58:29Z")

</div>

We just tried to ingest SQL data into Elasticsearch using Agent (SQL Input Integration).  
What I observed is that it stores the same set of data repeatedly.

For Example, if I have 5 rows in the SQL table, the first time it is ingesting the first 5 rows, it repeats again (keep on ingesting the 5 rows again).  
Is there anyway to configure the agent accordingly to ingest only 5 rows and incremental data only?

I made changes to the SQL query, but they were of no use.

Finally, in the SQL Input Integration, is there a way to hide the password where, within hosts, we are openly giving the password?

Are there any alternative ways to ingest through integrations other than depending on Logstash?

---

<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:** [September 12, 2023, 8:59am UTC](https://discuss.elastic.co/t/ingesting-data-using-agent-sql-input-integration/340820/2 "2023-09-12T08:59:08Z")

</div>

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