<?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 When Migrating from Splunk DBv2 Connect to DBv3 in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/When-Migrating-from-Splunk-DBv2-Connect-to-DBv3/m-p/594143#M25551</link>
    <description>&lt;P&gt;The new DBv3 doesn't like inline comments (--) in the SQL query you must update the query to user&amp;nbsp; multi-line comments to save the queries.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Use This:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;/* your SQL STATEMENT COMMENT */&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Not This:&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;--your SQL comment here&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Once the comment have been cleaned up you should be able to run your queries again.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Note: if you're using queries configured with rising columns watch the below video on YouTube by the Splunk team.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.youtube.com/watch?v=oPB2Lpd9ZAs" target="_blank" rel="noopener"&gt;https://www.youtube.com/watch?v=oPB2Lpd9ZAs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;good luck!&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 18 Apr 2022 18:59:42 GMT</pubDate>
    <dc:creator>rthomas247</dc:creator>
    <dc:date>2022-04-18T18:59:42Z</dc:date>
    <item>
      <title>When Migrating from Splunk DBv2 Connect to DBv3</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/When-Migrating-from-Splunk-DBv2-Connect-to-DBv3/m-p/594143#M25551</link>
      <description>&lt;P&gt;The new DBv3 doesn't like inline comments (--) in the SQL query you must update the query to user&amp;nbsp; multi-line comments to save the queries.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Use This:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;/* your SQL STATEMENT COMMENT */&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Not This:&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;--your SQL comment here&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Once the comment have been cleaned up you should be able to run your queries again.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Note: if you're using queries configured with rising columns watch the below video on YouTube by the Splunk team.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.youtube.com/watch?v=oPB2Lpd9ZAs" target="_blank" rel="noopener"&gt;https://www.youtube.com/watch?v=oPB2Lpd9ZAs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;good luck!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Apr 2022 18:59:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/When-Migrating-from-Splunk-DBv2-Connect-to-DBv3/m-p/594143#M25551</guid>
      <dc:creator>rthomas247</dc:creator>
      <dc:date>2022-04-18T18:59:42Z</dc:date>
    </item>
  </channel>
</rss>

