[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 434
  • Last Modified:

Transaction log

How do I limit the size of a transaction log? How do I configure what happens when that size is reached? Is there an option that allows me to push out the eldest transaction, as the most recent comes in?

Thanks,

Christo Fourie.
0
idsafs
Asked:
idsafs
1 Solution
 
QlemoC++ DeveloperCommented:
* Limit size: DB properties -> Files, look for type = log, on the right there shoukld be a button to change the size limit.

* you cannot configure the reaction if max log file size is reached. The DBMS will reject any changing SQL command till space is freed in the log, or the size limit is removed.

* When DB recovery mode is "Simple", the transaction log space is freed as soon as possible. All other recovery models require you to backup the transaction log to free space.
0
 
badbearontourCommented:
Hi,

Microsoft SQL Server Mananger
right mouse click on your database
Select Files in the popup database properties
Look at the grid and you will see the auto growth columns clcik on the button at the end of the box and on the log row, you will see your options

There is no option for a circular log, that would endanger you to not being able to recover a database! but you can grow a log at a certain rate or cap it at a size, but beware if the log fills up the database will stop

BB
0
 
JulianvaCommented:
You can limit the size using enterprise manager (sql 2000) or management studio(sql 2005)

right click on the database - chose properties - then chose transaction log - you will see the radio button to limit the size of the log file.

No there is no option to push out the oldest transaction.
you can truncate the entire log file.
you can also set the database to use simple or bullk logged recovery modes - so that sql server does not log every transaction. To do this you need to determine if at any time you will need to recover the database to a point in time.



0
 
idsafsAuthor Commented:
Hi.

Thanks for your replies! I misunderstood my superior. !The transaction log is not the problem, but this :

What our issue is is that the tempdb fills up as we go along Basically, from what I understand, the tempdb is created new each time the server starts, this then grows as things are done in any active db.  It is this growing that we need to restrict, nothing to do with the active/production db.

Any ideas?
0
 
JulianvaCommented:
where is you tempdb database files situated.  you can move the temp db to a drive that has enough space to accomodate the growth of tempdb and leave the growth option to unrestricted..

You can also create a maintenance job to truncate the tempdb and shrink it.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

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