<@U04SE163WC8> hey, does the sync mode deduped his...
# ask-ai
t
@kapa.ai hey, does the sync mode deduped history still exist and is it available for connection from sql server to snowflake ?
k
Based on the provided knowledge sources, the sync mode Incremental - Deduped History (also referred to as Incremental Sync - Append + Deduped) is supported for the Snowflake destination. This is confirmed in the documentation for Snowflake's supported sync modes: > The Snowflake destination supports the following sync modes: > - [Full Refresh - Overwrite](https://docs.airbyte.com/understanding-airbyte/connections/full-refresh-overwrite/) > - [Full Refresh - Append](https://docs.airbyte.com/understanding-airbyte/connections/full-refresh-append) > - [Incremental Sync - Append](https://docs.airbyte.com/understanding-airbyte/connections/incremental-append) > - [Incremental Sync - Append + Deduped](https://docs.airbyte.com/understanding-airbyte/connections/incremental-append-deduped) However, there is no specific information in the provided knowledge sources about the availability of this sync mode for a connection from SQL Server to Snowflake. The knowledge sources do not mention SQL Server in this context. For the most accurate and up-to-date information, I recommend checking the [Airbyte documentation](https://docs.airbyte.com/) or reaching out to the Airbyte support team directly. If you have any other questions or need further assistance, feel free to ask!
t
@kapa.ai deduped history and Incremental Sync - Append + Deduped modes are the same ?
k
A message from kapa.ai
Yes, Incremental Sync - Deduped History and Incremental Sync - Append + Deduped modes refer to the same concept. Here is a detailed explanation based on the provided knowledge sources: 1. Incremental Sync - Append + Deduped: - Incremental: Syncs only new or modified data, preventing re-fetching data that has already been replicated. - Append: Adds this incremental data to existing tables in your data warehouse. - Deduped: Ensures that data in the final table is unique per primary key by sorting the data using the cursor field and keeping only the latest de-duplicated data row. Source: [Incremental Sync - Append + Deduped Overview](https://docs.airbyte.com/using-airbyte/core-concepts/sync-modes/incremental-append-deduped#overview) 2. Incremental Sync - Deduped History: - Generates two normalized destination tables: a history table (also known as the SCD table) and a deduped table. - The history table includes historical versions of each record with start and end dates. - The deduped table contains a single copy of each record. Source: [Incremental Sync - Deduped History](https://airbyte.com/tutorials/incremental-data-synchronization#step-2) Both modes aim to ensure that the final table contains unique records per primary key, with historical data being managed separately. If you have any further questions or need additional clarification, feel free to ask!