<?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 SQL Transaction Log Size with SIM 4.1 in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/sql-transaction-log-size-with-sim-4-1/m-p/3394714#M6511</link>
    <description>We are running an installation of HP Systems Insight Manager on a Windows 2003 server, the database backend is Microsoft SQL 2000.  There are currently 135 managed servers in Insight but this will be increased to ~300.&lt;BR /&gt;&lt;BR /&gt;The database itself is quite small (130Mb) but the transaction logs are growing at a impressive rate (~12Gb Per Day), the database is set to 'Full Recovery Model' and we are doing nightly backups of the logs with trasaction log truncation switched on which is working well.&lt;BR /&gt;&lt;BR /&gt;Does anyone have any idea why the transaction logs are growing so fast and how I can slow it down.  It is not currently an issue but if the backups fail or we add more managed server I can see it growing at a crazy rate, this is when it will become an issue for me.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;BR /&gt;Regards&lt;BR /&gt;Matthew&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 06 Oct 2004 11:02:17 GMT</pubDate>
    <dc:creator>Matthew Hartley</dc:creator>
    <dc:date>2004-10-06T11:02:17Z</dc:date>
    <item>
      <title>SQL Transaction Log Size with SIM 4.1</title>
      <link>https://community.hpe.com/t5/server-management-systems/sql-transaction-log-size-with-sim-4-1/m-p/3394714#M6511</link>
      <description>We are running an installation of HP Systems Insight Manager on a Windows 2003 server, the database backend is Microsoft SQL 2000.  There are currently 135 managed servers in Insight but this will be increased to ~300.&lt;BR /&gt;&lt;BR /&gt;The database itself is quite small (130Mb) but the transaction logs are growing at a impressive rate (~12Gb Per Day), the database is set to 'Full Recovery Model' and we are doing nightly backups of the logs with trasaction log truncation switched on which is working well.&lt;BR /&gt;&lt;BR /&gt;Does anyone have any idea why the transaction logs are growing so fast and how I can slow it down.  It is not currently an issue but if the backups fail or we add more managed server I can see it growing at a crazy rate, this is when it will become an issue for me.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;BR /&gt;Regards&lt;BR /&gt;Matthew&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 06 Oct 2004 11:02:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/sql-transaction-log-size-with-sim-4-1/m-p/3394714#M6511</guid>
      <dc:creator>Matthew Hartley</dc:creator>
      <dc:date>2004-10-06T11:02:17Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Transaction Log Size with SIM 4.1</title>
      <link>https://community.hpe.com/t5/server-management-systems/sql-transaction-log-size-with-sim-4-1/m-p/3394715#M6512</link>
      <description>You should really consider changing the database recovery model to simple.  The rapidly growing transaction log is a known issue with SIM.</description>
      <pubDate>Wed, 06 Oct 2004 11:14:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/sql-transaction-log-size-with-sim-4-1/m-p/3394715#M6512</guid>
      <dc:creator>Joel Rubenstein</dc:creator>
      <dc:date>2004-10-06T11:14:33Z</dc:date>
    </item>
  </channel>
</rss>

