<?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 Cached search results in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Cached-search-results/m-p/72665#M18179</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I am using time consuming searches and i was wondering if and how is it possible to run the searches in advance and then access the cached search results without running the search again.
I saw the saved searches option but i was not sure whether they accomplish what i am looking for.&lt;/P&gt;

&lt;P&gt;Thanks for your help!&lt;/P&gt;</description>
    <pubDate>Tue, 19 Oct 2010 18:05:42 GMT</pubDate>
    <dc:creator>Eldad</dc:creator>
    <dc:date>2010-10-19T18:05:42Z</dc:date>
    <item>
      <title>Cached search results</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Cached-search-results/m-p/72665#M18179</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I am using time consuming searches and i was wondering if and how is it possible to run the searches in advance and then access the cached search results without running the search again.
I saw the saved searches option but i was not sure whether they accomplish what i am looking for.&lt;/P&gt;

&lt;P&gt;Thanks for your help!&lt;/P&gt;</description>
      <pubDate>Tue, 19 Oct 2010 18:05:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Cached-search-results/m-p/72665#M18179</guid>
      <dc:creator>Eldad</dc:creator>
      <dc:date>2010-10-19T18:05:42Z</dc:date>
    </item>
    <item>
      <title>Re: Cached search results</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Cached-search-results/m-p/72666#M18180</link>
      <description>&lt;P&gt;You can use the &lt;A href="http://www.splunk.com/base/Documentation/latest/SearchReference/Loadjob" rel="nofollow"&gt;loadjob&lt;/A&gt; search command to load a previous search. Keep in mind that there are default values for the time search results are kept around, and that the user's disk quota will play a part as well. Rather then replicating previous posts, have a look at the answers to this question for more info on tweaking the cache durations: &lt;A href="http://answers.splunk.com/questions/7526/how-do-you-increase-the-duration-that-a-search-sticks-around-the-server" rel="nofollow"&gt;http://answers.splunk.com/questions/7526/how-do-you-increase-the-duration-that-a-search-sticks-around-the-server&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Oct 2010 20:06:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Cached-search-results/m-p/72666#M18180</guid>
      <dc:creator>ftk</dc:creator>
      <dc:date>2010-10-19T20:06:01Z</dc:date>
    </item>
    <item>
      <title>Re: Cached search results</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Cached-search-results/m-p/72667#M18181</link>
      <description>&lt;P&gt;Saved searches will be persisted until your quota settings rotate out the old searches based on the period settings.   This is probably the most consistent way to have a search persisted and be able to load it at a future point in time.   To load it in the future, you can view it through the jobs viewer in the gui or via the loadjob search command.  &lt;/P&gt;

&lt;P&gt;Note - simple dashboards that leverage scheduled saved searches will utilize the last run search.  I believe the setting is called "useHistory".  This may be a bit easier to use from an interface standpoint, as a user can just load that dashboard at any point in time to see the last stored result set for a given set of search results.  &lt;/P&gt;</description>
      <pubDate>Wed, 20 Oct 2010 06:55:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Cached-search-results/m-p/72667#M18181</guid>
      <dc:creator>Simeon</dc:creator>
      <dc:date>2010-10-20T06:55:26Z</dc:date>
    </item>
  </channel>
</rss>

