• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 313
  • Last Modified:

high transactions on our database

I just received the following email from my hosting company.

I have 2 questions.

1) In general what would cause transaction logs being so high
2) what are the effects of being in simple recovery model.

"Can i ask precisely what you're doing with the xxxx database at present ?

Yesterday some 77GB of transaction logs were generated, today has been 10GB - which is more than all the other databases on the server !

To ensure this database doesn't affect other users on the server, i've had to set your database to use a simple recovery model..."
  • 2
1 Solution
lcohanDatabase AnalystCommented:
1. Insert/update/deletes are all logged transactions in SQL plust other operations like some DDL changes and a re-index for instance.

2. Setting database to Simple recovery will reduce somewhat transaction logging however this may impact your disaster recovery/point in time restore/log shipping capabilities.

larry urbanDevOps EngineerCommented:
The log is so large because backups are not scheduled to run on it or not often enough.
When my logs fail to back up, they will grow uncontrollably. Just last week, rights on the backup server were modified and I didn't catch it until the next day. The logs consumed the entire log drive, an extra 150 GB in 18 hours. Once I discovered the problem, I had to do a full backup and then another transaction log backup before I was able to shrink the log file back down to the appropriate size.

I believe @Todar is correct in that your hosting company is not backing up the logs frequently enough to keep them small. As @Icohan indicated, simply recovery will prevent restoring to a point in time other than your full backup.
lcohanDatabase AnalystCommented:
Backing up the db's and t-logs should not be left for the hosting company to do but the owner of the database business rules should drive the backup/restore from disaster recovery point of view nut just regular maintenance. Backing up regularely the T-Logs will reduce the amount of disk space the T-logs are taking and indeed keep that under control but will NOT eliminate excessive logging. For that you may need to do a code review and eliminate unnecessary transactions that are filling up your t-logs.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now