<?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 Re: SQL Status in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/SQL-Status/m-p/455833#M6941</link>
    <description>&lt;P&gt;@noy72, Did it work?  If so, please accept the answer to help future readers.&lt;/P&gt;</description>
    <pubDate>Fri, 15 Feb 2019 13:41:50 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2019-02-15T13:41:50Z</dc:date>
    <item>
      <title>SQL Status</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/SQL-Status/m-p/455830#M6938</link>
      <description>&lt;P&gt;Good day,&lt;/P&gt;

&lt;P&gt;I am brand new to Splunk. I am constructing a dashboard to monitor the status of our SCCM environment. I have so far figured out monitoring event logs and serviceaccount stats. My current challenge is verifying the status of the CM database. I am not trying to index the database into Splunk, although we have the Splunk DB Connect App installed if that is what needs to happen. I just want to be able to look at the dashboard and see that CM_* is OnLine.&lt;/P&gt;

&lt;P&gt;I appreciate any assistance that might be afforded to me.&lt;/P&gt;

&lt;P&gt;Ron Jones&lt;/P&gt;</description>
      <pubDate>Thu, 07 Feb 2019 19:45:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/SQL-Status/m-p/455830#M6938</guid>
      <dc:creator>noy72</dc:creator>
      <dc:date>2019-02-07T19:45:19Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Status</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/SQL-Status/m-p/455831#M6939</link>
      <description>&lt;P&gt;The SCCM App for Splunk (&lt;A href="https://splunkbase.splunk.com/app/2750/"&gt;https://splunkbase.splunk.com/app/2750/&lt;/A&gt;) is a bit old, but may give you some ideas about how to solve your problem.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Feb 2019 05:59:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/SQL-Status/m-p/455831#M6939</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-02-08T05:59:09Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Status</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/SQL-Status/m-p/455832#M6940</link>
      <description>&lt;P&gt;I'll instal it today. Loking at what's available on ine I'll still need to do somework, but it is a start.&lt;BR /&gt;
Thank you&lt;/P&gt;</description>
      <pubDate>Fri, 08 Feb 2019 18:16:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/SQL-Status/m-p/455832#M6940</guid>
      <dc:creator>noy72</dc:creator>
      <dc:date>2019-02-08T18:16:10Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Status</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/SQL-Status/m-p/455833#M6941</link>
      <description>&lt;P&gt;@noy72, Did it work?  If so, please accept the answer to help future readers.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Feb 2019 13:41:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/SQL-Status/m-p/455833#M6941</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-02-15T13:41:50Z</dc:date>
    </item>
  </channel>
</rss>

