<?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 Hello,
We had similar issues… in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Error-Related-to-Blue-Prism-Database/m-p/81637#M33184</link>
    <description>Hello,
We had similar issues and crashes on our server due to excessive logging, I am only a beginner and this&amp;nbsp;might not be relevant but no one has replied to this thread yet I wanted to try and help.
If you have not already tried this, consider disabling logging except for errors across the entire process.&amp;nbsp; Only enable logging on vital actions that you want to track.
We had a problem where there was so much excessive logging, the resource was spending ~75% of its time recording what it was doing and waiting for DB server responses&amp;nbsp;rather than doing anything useful. The&amp;nbsp;process was logging 100-200 MB of data per minute and crashing our server daily.
Now it grows much more slowly and the process runs almost 4x faster than before.
Hope this helps in some way!</description>
    <pubDate>Sun, 27 Jan 2019 05:52:00 GMT</pubDate>
    <dc:creator>BenKirimlidis</dc:creator>
    <dc:date>2019-01-27T05:52:00Z</dc:date>
    <item>
      <title>Error Related to Blue Prism Database</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Error-Related-to-Blue-Prism-Database/m-p/81636#M33183</link>
      <description>When started designing the solution the size was 500 MB along with the log file, after completion its size increased to 1.6 GB with the log.
Now the solution was in production and its size is 1.96 GB, now the size was increased so much so that the solution has become very slow, and blue prism was throwing an error.
Once the error was closed its closing the Blue Prism.
Once we run BP again, then speed was in normal same as we run it for the very first time.&amp;nbsp;

&amp;nbsp;

There might be a chance of increase in the size of databased in future.

So, If there is any solution to the above issue will be helpful.

&amp;nbsp;

Error related screenshot is attached for reference.</description>
      <pubDate>Fri, 17 Aug 2018 15:10:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Error-Related-to-Blue-Prism-Database/m-p/81636#M33183</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-08-17T15:10:00Z</dc:date>
    </item>
    <item>
      <title>Hello,
We had similar issues…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Error-Related-to-Blue-Prism-Database/m-p/81637#M33184</link>
      <description>Hello,
We had similar issues and crashes on our server due to excessive logging, I am only a beginner and this&amp;nbsp;might not be relevant but no one has replied to this thread yet I wanted to try and help.
If you have not already tried this, consider disabling logging except for errors across the entire process.&amp;nbsp; Only enable logging on vital actions that you want to track.
We had a problem where there was so much excessive logging, the resource was spending ~75% of its time recording what it was doing and waiting for DB server responses&amp;nbsp;rather than doing anything useful. The&amp;nbsp;process was logging 100-200 MB of data per minute and crashing our server daily.
Now it grows much more slowly and the process runs almost 4x faster than before.
Hope this helps in some way!</description>
      <pubDate>Sun, 27 Jan 2019 05:52:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Error-Related-to-Blue-Prism-Database/m-p/81637#M33184</guid>
      <dc:creator>BenKirimlidis</dc:creator>
      <dc:date>2019-01-27T05:52:00Z</dc:date>
    </item>
  </channel>
</rss>

