<?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>Question Re: Why was the V17 default parameterization_level changed? in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/why-was-the-v17-default-parameterization-level-changed/qaa-p/13815272#M4846115</link>
    <description>&lt;P&gt;The change in the default value was a side effect of a change made for IQ. &lt;EM&gt;It was &lt;STRONG&gt;not&lt;/STRONG&gt; because it was unsafe.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;There was one defect with parameteritization_Level that was not in the release notes - it will be documented in the future SP. That issue:&lt;/P&gt;
&lt;DIV&gt;&lt;PRE&gt;&lt;SPAN&gt;&lt;/SPAN&gt;================(Build #4919  - Engineering Case #817663)================

If statement was automatically parameterized (parameterization_level Simple 
or Forced) and a parameter value was larger than 250 bytes, it is possible 
that a SQLE_COMMUNICATION_ERROR would be incorrectly reported.  A workaround 
is to set parameterization_level to Off.  This has been fixed.
&lt;/PRE&gt;&lt;/DIV&gt;</description>
    <pubDate>Mon, 29 Jul 2019 06:41:43 GMT</pubDate>
    <dc:creator>chris_keating</dc:creator>
    <dc:date>2019-07-29T06:41:43Z</dc:date>
    <item>
      <title>Why was the V17 default parameterization_level changed?</title>
      <link>https://community.sap.com/t5/technology-q-a/why-was-the-v17-default-parameterization-level-changed/qaq-p/13815271</link>
      <description>&lt;P&gt;When V17 was introduced, the default for the new parameterization_level was "Simple".&lt;/P&gt;
&lt;P&gt;The default has since been changed to 'Off'... why is that?&lt;/P&gt;
&lt;P&gt;Is parameterization_level is &lt;B&gt;unsafe to use? &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/B&gt;&lt;/P&gt;
&lt;P&gt;&lt;IMG width="400" src="https://cdn.ebaumsworld.com/mediaFiles/picture/218923/81025859.jpg" /&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 28 Jul 2019 11:49:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/why-was-the-v17-default-parameterization-level-changed/qaq-p/13815271</guid>
      <dc:creator>Breck_Carter</dc:creator>
      <dc:date>2019-07-28T11:49:43Z</dc:date>
    </item>
    <item>
      <title>Re: Why was the V17 default parameterization_level changed?</title>
      <link>https://community.sap.com/t5/technology-q-a/why-was-the-v17-default-parameterization-level-changed/qaa-p/13815272#M4846115</link>
      <description>&lt;P&gt;The change in the default value was a side effect of a change made for IQ. &lt;EM&gt;It was &lt;STRONG&gt;not&lt;/STRONG&gt; because it was unsafe.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;There was one defect with parameteritization_Level that was not in the release notes - it will be documented in the future SP. That issue:&lt;/P&gt;
&lt;DIV&gt;&lt;PRE&gt;&lt;SPAN&gt;&lt;/SPAN&gt;================(Build #4919  - Engineering Case #817663)================

If statement was automatically parameterized (parameterization_level Simple 
or Forced) and a parameter value was larger than 250 bytes, it is possible 
that a SQLE_COMMUNICATION_ERROR would be incorrectly reported.  A workaround 
is to set parameterization_level to Off.  This has been fixed.
&lt;/PRE&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 29 Jul 2019 06:41:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/why-was-the-v17-default-parameterization-level-changed/qaa-p/13815272#M4846115</guid>
      <dc:creator>chris_keating</dc:creator>
      <dc:date>2019-07-29T06:41:43Z</dc:date>
    </item>
    <item>
      <title>Re: Why was the V17 default parameterization_level changed?</title>
      <link>https://community.sap.com/t5/technology-q-a/why-was-the-v17-default-parameterization-level-changed/qaa-p/13815273#M4846116</link>
      <description>&lt;P&gt;Thank you for the information it was very useful..&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2019 06:27:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/why-was-the-v17-default-parameterization-level-changed/qaa-p/13815273#M4846116</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2019-08-01T06:27:30Z</dc:date>
    </item>
  </channel>
</rss>

