# CData Sync - Missing values on Snowflake destination

**URL:** <https://community.cdata.com/t/cdata-sync-missing-values-on-snowflake-destination/458>\
**Category:** Editions\
**Tags:** article, cdata-sync, snowflake\
**Created:** [October 13, 2023, 5:59pm UTC](https://community.cdata.com/t/cdata-sync-missing-values-on-snowflake-destination/458 "2023-10-13T17:59:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bukuroshe\_D](https://avatars.discourse-cdn.com/v4/letter/b/50afbb/32.png) [@Bukuroshe\_D](https://community.cdata.com/u/Bukuroshe_D)\
**Post date:** [October 13, 2023, 5:59pm UTC](https://community.cdata.com/t/cdata-sync-missing-values-on-snowflake-destination/458/1 "2023-10-13T17:59:03Z")

</div>

When using _CData SYNC_ and replicating to a Snowflake Destination, you may notice that even though the job has run successfully, and the schema of the table in Snowflake has been created, you are still not able to see and load the data.

This is likely caused by a casing issue as Snowflake expects data to be capitalized for setting certain fields. This can lead to data failing to show up in the Snowflake destination.

To resolve this issue, you can set the _ **Ignore Case** _ property in your advanced Snowflake connection settings **to _True_** as show in the following screenshot:

 ![8a206086-c864-46e7-9a50-55d8d0221b66.png](https://us1.discourse-cdn.com/cdata/original/1X/0b7e105e095ff277244541f237d59c9d8c56c79a.png)

This setting directly maps to the [QUOTED\_IDENTIFIERS\_IGNORE\_CASE](https://docs.snowflake.com/en/sql-reference/parameters.html#quoted-identifiers-ignore-case) property in Snowflake and specifies whether Snowflake will treat identifiers as case sensitive. Its default value is false _making Snowflake more sensitive to casing issues in some cases._

Please reach out to [support@cdata.com](mailto:support@cdata.com) if this does not resolve the problem for you.