HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: SQL Transaction Log Size with SIM 4.1
Server Management - Systems Insight Manager
1833777
Members
1982
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2004 04:02 AM
10-06-2004 04:02 AM
SQL Transaction Log Size with SIM 4.1
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.
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.
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.
Thanks in advance
Regards
Matthew
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.
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.
Thanks in advance
Regards
Matthew
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2004 04:14 AM
10-06-2004 04:14 AM
Re: SQL Transaction Log Size with SIM 4.1
You should really consider changing the database recovery model to simple. The rapidly growing transaction log is a known issue with SIM.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP