<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Why are VARCHAR lengths from Snowflake tripled in SAS DI Studio? in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/Why-are-VARCHAR-lengths-from-Snowflake-tripled-in-SAS-DI-Studio/m-p/967212#M21045</link>
    <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I’m accessing Snowflake tables through SAS Data Integration Studio using the Snowflake connector.&lt;/P&gt;&lt;P&gt;When I register&amp;nbsp; table from Snowflake in SAS DI, I noticed that VARCHAR(n) columns are automatically assigned LENGTH=3n in SAS metadata.&lt;BR /&gt;For example: VARCHAR(2) becomes LENGTH=6.&lt;/P&gt;&lt;P&gt;Why does this happen, even though both systems use UTF-8?&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
    <pubDate>Thu, 22 May 2025 13:03:19 GMT</pubDate>
    <dc:creator>jozumfoen</dc:creator>
    <dc:date>2025-05-22T13:03:19Z</dc:date>
    <item>
      <title>Why are VARCHAR lengths from Snowflake tripled in SAS DI Studio?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Why-are-VARCHAR-lengths-from-Snowflake-tripled-in-SAS-DI-Studio/m-p/967212#M21045</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I’m accessing Snowflake tables through SAS Data Integration Studio using the Snowflake connector.&lt;/P&gt;&lt;P&gt;When I register&amp;nbsp; table from Snowflake in SAS DI, I noticed that VARCHAR(n) columns are automatically assigned LENGTH=3n in SAS metadata.&lt;BR /&gt;For example: VARCHAR(2) becomes LENGTH=6.&lt;/P&gt;&lt;P&gt;Why does this happen, even though both systems use UTF-8?&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 13:03:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Why-are-VARCHAR-lengths-from-Snowflake-tripled-in-SAS-DI-Studio/m-p/967212#M21045</guid>
      <dc:creator>jozumfoen</dc:creator>
      <dc:date>2025-05-22T13:03:19Z</dc:date>
    </item>
    <item>
      <title>Why are VARCHAR lengths from Snowflake tripled in SAS DI Studio?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Why-are-VARCHAR-lengths-from-Snowflake-tripled-in-SAS-DI-Studio/m-p/967214#M21048</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I’m accessing Snowflake tables through SAS Data Integration Studio using the Snowflake connector.&lt;/P&gt;&lt;P&gt;When I register&amp;nbsp; table from Snowflake in SAS DI, I noticed that VARCHAR(n) columns are automatically assigned LENGTH=3n in SAS metadata.&lt;BR /&gt;For example: VARCHAR(2) becomes LENGTH=6. Why does this happen, even though both systems use UTF-8?&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 13:20:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Why-are-VARCHAR-lengths-from-Snowflake-tripled-in-SAS-DI-Studio/m-p/967214#M21048</guid>
      <dc:creator>jozumfoen</dc:creator>
      <dc:date>2025-05-22T13:20:51Z</dc:date>
    </item>
    <item>
      <title>Re: Why are VARCHAR lengths from Snowflake tripled in SAS DI Studio?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Why-are-VARCHAR-lengths-from-Snowflake-tripled-in-SAS-DI-Studio/m-p/967217#M21046</link>
      <description>&lt;P&gt;My first idea would be that Snowflake counts&amp;nbsp;&lt;EM&gt;UTF characters&lt;/EM&gt;, while SAS counts&amp;nbsp;&lt;EM&gt;bytes&lt;/EM&gt;.&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 13:40:54 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Why-are-VARCHAR-lengths-from-Snowflake-tripled-in-SAS-DI-Studio/m-p/967217#M21046</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2025-05-22T13:40:54Z</dc:date>
    </item>
    <item>
      <title>Re: Why are VARCHAR lengths from Snowflake tripled in SAS DI Studio?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Why-are-VARCHAR-lengths-from-Snowflake-tripled-in-SAS-DI-Studio/m-p/967260#M21047</link>
      <description>&lt;P&gt;We use SAS/ACCESS Interface to Snowflake too and see the same behaviour.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A Google search suggests that this could be standard Snowflake behaviour:&amp;nbsp;&lt;A href="https://community.snowflake.com/s/article/Varchar-length-implicitly-increases-if-column-is-Uppercased" target="_blank"&gt;https://community.snowflake.com/s/article/Varchar-length-implicitly-increases-if-column-is-Uppercased&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 20:14:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Why-are-VARCHAR-lengths-from-Snowflake-tripled-in-SAS-DI-Studio/m-p/967260#M21047</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2025-05-22T20:14:55Z</dc:date>
    </item>
    <item>
      <title>Re: Why are VARCHAR lengths from Snowflake tripled in SAS DI Studio?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Why-are-VARCHAR-lengths-from-Snowflake-tripled-in-SAS-DI-Studio/m-p/967481#M21052</link>
      <description>&lt;P&gt;It's certainly worth to look into options&amp;nbsp;&lt;A href="https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/acreldb/n03byaxn5439w5n1ev20fyqk0uaf.htm" target="_self"&gt;DBCLIENT_MAX_BYTES&lt;/A&gt; and&amp;nbsp;&lt;A href="https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/acreldb/n12a1h1cyqucyzn1gr9ih9wys73n.htm" target="_self"&gt;DBSERVER_MAX_BYTES&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 May 2025 07:37:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Why-are-VARCHAR-lengths-from-Snowflake-tripled-in-SAS-DI-Studio/m-p/967481#M21052</guid>
      <dc:creator>Patrick</dc:creator>
      <dc:date>2025-05-26T07:37:32Z</dc:date>
    </item>
  </channel>
</rss>

