<?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 Escape special characters in DB Connect in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Escape-special-characters-in-DB-Connect/m-p/573022#M101372</link>
    <description>&lt;P&gt;Pulling database events with Splunk DB Connect I noticed that:&lt;BR /&gt;&lt;BR /&gt;1. New (non-existing) fields are created&lt;BR /&gt;2. text fields containing special characters&amp;nbsp; are cut&lt;BR /&gt;&lt;BR /&gt;The only reason I have been able to identify consists in the presence of special characters of the kind:&lt;BR /&gt;( ) " :&lt;BR /&gt;... in fields like "SQL _Text", that by their nature can contain quotes, brackets and else.&lt;/P&gt;&lt;P&gt;How can I escape these problem-causing characters ?&lt;BR /&gt;This done inside Splunk - and not anywhere on the DB side, or the SQL command for pulling records.&lt;BR /&gt;&lt;BR /&gt;What are the characters that must be escaped?&lt;BR /&gt;Asking the later because when working&amp;nbsp;in a previous project with ingesting events from a DB to Splunk via TCP Data Input, I noticed that not all special characters where causing same problem as above - but only few of them.&lt;BR /&gt;&lt;BR /&gt;best regards&lt;BR /&gt;Altin&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 29 Oct 2021 19:25:41 GMT</pubDate>
    <dc:creator>altink</dc:creator>
    <dc:date>2021-10-29T19:25:41Z</dc:date>
    <item>
      <title>Escape special characters in DB Connect</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Escape-special-characters-in-DB-Connect/m-p/573022#M101372</link>
      <description>&lt;P&gt;Pulling database events with Splunk DB Connect I noticed that:&lt;BR /&gt;&lt;BR /&gt;1. New (non-existing) fields are created&lt;BR /&gt;2. text fields containing special characters&amp;nbsp; are cut&lt;BR /&gt;&lt;BR /&gt;The only reason I have been able to identify consists in the presence of special characters of the kind:&lt;BR /&gt;( ) " :&lt;BR /&gt;... in fields like "SQL _Text", that by their nature can contain quotes, brackets and else.&lt;/P&gt;&lt;P&gt;How can I escape these problem-causing characters ?&lt;BR /&gt;This done inside Splunk - and not anywhere on the DB side, or the SQL command for pulling records.&lt;BR /&gt;&lt;BR /&gt;What are the characters that must be escaped?&lt;BR /&gt;Asking the later because when working&amp;nbsp;in a previous project with ingesting events from a DB to Splunk via TCP Data Input, I noticed that not all special characters where causing same problem as above - but only few of them.&lt;BR /&gt;&lt;BR /&gt;best regards&lt;BR /&gt;Altin&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 29 Oct 2021 19:25:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Escape-special-characters-in-DB-Connect/m-p/573022#M101372</guid>
      <dc:creator>altink</dc:creator>
      <dc:date>2021-10-29T19:25:41Z</dc:date>
    </item>
  </channel>
</rss>

