# Incremental Refresh Date Logic

**URL:** <https://community.amazonquick.com/t/incremental-refresh-date-logic/49941>\
**Category:** Q&A\
**Tags:** data-accessor, developer, quick-sight\
**Created:** [October 6, 2025, 10:42am UTC](https://community.amazonquick.com/t/incremental-refresh-date-logic/49941 "2025-10-06T10:42:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark-Hayward](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@Mark-Hayward](https://community.amazonquick.com/u/Mark-Hayward)\
**Post date:** [October 6, 2025, 10:42am UTC](https://community.amazonquick.com/t/incremental-refresh-date-logic/49941/1 "2025-10-06T10:42:50Z")

</div>

Hello

I am struggling to find a definitive answer on this and I was hoping someone could help me.

When we perform an incremental refresh on a SQL table, does Quicksight pass the date of the window start as a parameter to the underlying query, or does it pull all the data from the database and only load the data from the window start time into SPICE?

I am trying to reduce the load on my database, and I don’t quite understand whether incremental refresh is only used when loading data from the database into Spice after the query is run, or if it actually passes the date into the underlying query so that the database returns fewer rows. Can anybody confirm how it works?

---

<div class="post-metadata">

**Author:** ![Xclipse](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/xclipse/32/20455_2.png) [@Xclipse](https://community.amazonquick.com/u/Xclipse)\
**Post date:** [October 6, 2025, 1:22pm UTC](https://community.amazonquick.com/t/incremental-refresh-date-logic/49941/2 "2025-10-06T13:22:03Z")

</div>

Hi @Mark-Hayward

Quick Sight performs incremental refresh by passing the window start date as a filter (typically in the form of a WHERE clause on the chosen timestamp column) directly in the SQL query to the underlying database, so only the data changed or added since the last refresh window is retrieved and loaded into SPICE. This means the database itself handles the filtering and returns only relevant records, minimizing database load, reducing row volume, and speeding up SPICE refresh rather than pulling the entire dataset and filtering it after retrieval.

Please refer to the below documentation this might be helpful for you.

> **[Refreshing SPICE data - Amazon QuickSight](https://docs.aws.amazon.com/quicksight/latest/user/refreshing-imported-data.html)**
>
> Refresh data in Amazon QuickSight.

---

<div class="post-metadata">

**Author:** ![Brett](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/brett/32/36494_2.png) [@Brett](https://community.amazonquick.com/u/Brett)\
**Post date:** [October 22, 2025, 5:59pm UTC](https://community.amazonquick.com/t/incremental-refresh-date-logic/49941/3 "2025-10-22T17:59:22Z")

</div>

Hi @Mark-Hayward,

Following up here as it’s been awhile since we last heard from you on this thread; did you have any additional questions regarding your initial post?

If we do not hear back within the next 3 business days, I’ll close out this topic.

Thank you

---

<div class="post-metadata">

**Author:** ![Brett](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/brett/32/36494_2.png) [@Brett](https://community.amazonquick.com/u/Brett)\
**Post date:** [October 27, 2025, 6:13pm UTC](https://community.amazonquick.com/t/incremental-refresh-date-logic/49941/4 "2025-10-27T18:13:45Z")

</div>

Hi @Mark-Hayward,

Since we have not heard back, I’ll go ahead and close out this topic. However, if you have any additional questions, feel free to create a new post in the community.

Thank you