Transaction log size

Last Post 25 Jan 2013 11:26 AM by gunneyk. 6 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
sql-tips
New Member
New Member

--
23 Jan 2013 11:59 AM
the transaction log size increases very frequently. Size and frequent truncates are the issues with our client, making simple and truncating is becoming issue and client can't afford to increase the size of the disk. What are the most optimal solution without getting into any legal issues.

rm
New Member
New Member

--
24 Jan 2013 04:50 AM
How often do you backup log?
sql-tips
New Member
New Member

--
24 Jan 2013 07:25 AM
Every 15 minutes
rm
New Member
New Member

--
24 Jan 2013 07:40 AM
How big the log is? Just curious. If can't increase disk size, options left are reducing logging (set db to bulk-logged mode) or backup log more often. May worth to check what kind of transactions generated big logs.
sql-tips
New Member
New Member

--
25 Jan 2013 07:36 AM
Thanks.. How do we check transactions generated in the logs..
rm
New Member
New Member

--
25 Jan 2013 09:53 AM
With 'dbcc log' or third party tools.
gunneyk
New Member
New Member

--
25 Jan 2013 11:26 AM
What do you mean by frequent truncates is an issue? Are they truncating the log themselves? If so then that is a problem all in it;s own. Do they shrink the logs or have Autoshrink turned on? If so that is a problem as well. The log needs to be at what ever size it takes to do normal processing or any maintenance activities such as rebuilding indexes and such. The need to understand what is causing it to grow. Do they have long running open transactions that prevent log reuse?
You are not authorized to post a reply.

Acceptable Use Policy