Full refresh-overwrite sync in Airbyte retrieves all available data from the source, regardless of whether it has been synced before or not. This means that every time a sync is performed, the entire source dataset is copied and sent to the destination database. This approach may be infeasible for large amounts of data, and other replication modes, such as incremental sync, are likely to be more appropriate. For example, if the source dataset contains 10MB of data, and the replication frequency is every 5 minutes, then in one year there will have been 105,120 replication syncs. This means that there will be 105,120 full loads of data from the source to the destination, which means transmitting 10MB * 105,120 = 1,051,200 MB or approximately 1TB of data [^1^]. The load on the source database will depend on the size of the dataset and the frequency of the syncs. It's important to consider the impact on the source database and choose the appropriate replication mode and frequency based on your specific use case. [^1^]: [Full Data Synchronization Tutorial](https://airbyte.com/tutorials/full-data-synchronization)

New message text here

Hmm, I don't know enough to give you a confident answer yet about whether all

SELECT

queries for the 3 tables are run at once during the sync process. However, you can refer to the [Airbyte documentation](https://docs.airbyte.com) for more information on how the sync process works.

I apologize for not being able to provide a direct answer to your question about whether all

SELECT

queries for the 3 tables are run at once during the sync process. The information extracts provided do not cover this specific detail. I recommend referring to the [Airbyte documentation](https://docs.airbyte.com) or joining the [Airbyte Slack community](https://airbytehq.slack.com/ssb/redirect) to ask your question in the #getting-started channel for more assistance.