HELP!!!! Transaction Log Automatically Shrinking

Question

HELP!!!! Transaction Log Automatically Shrinking

Viewing 7 posts - 31 through 36 (of 36 total)

You must be logged in to reply to this topic. Login to reply

Lester Policarpio SSCertifiable Points: 7109 More actions · Answer 1

How can i save my t-log? b? simple recovery mode? what if i want a point in time recovery? Even backing up the database doesnt save the t-log?

"-=Still Learning=-"

Lester Policarpio

philcart SSC-Forever Points: 47794 More actions · Answer 2

Backing up the database is seperate to backing up the log.

Take a look at the following article,

http://msdn2.microsoft.com/en-us/library/ms191253.aspx

It's for SQL 2005, but most of it is applicable to SQL Server in general. It gives you a good overview of the recovery models and scenarios for restoring databases.

--------------------
Colt 45 - the original point and click interface

Lester Policarpio SSCertifiable Points: 7109 More actions · Answer 3

Thanks for the info and patience Phil now its clear to me about the difference of database backup and tlog backup. If i will not use the tlog i can use the simple recovery mode but im just wondering about BACKUP LOG WITH TRUNCATE_ONLY (just want added information) why does it shrink the total log size when i executed it in sql version 7.0?? Because i think its job is to only truncate the space used in a transaction log?

"-=Still Learning=-"

Lester Policarpio

philcart SSC-Forever Points: 47794 More actions · Answer 4

The transaction log is made up of multiple virtual log files (VLF). Without doing a lot of digging through old documentation, my guess would be that it's removing the empty VLF from the end of the file.

--------------------
Colt 45 - the original point and click interface

Lester Policarpio SSCertifiable Points: 7109 More actions · Answer 5

So in short its normal...?

What about this explanation??

From http://forums.devx.com/showthread.php?t=23773

Truncating the log does not reduce the physical file size. To do that you

will have to use DBCC SHRINKFILE. Truncating the log removes the inactive

portion of the transaction log, those transactions that have already been

terminated through commit or rollback. Normally this information is retained

in the event that the database must be restored from backup.

"-=Still Learning=-"

Lester Policarpio

philcart SSC-Forever Points: 47794 More actions · Answer 6

That post doesn't show what version of SQL they're talking about. Without reading up on old documentation, I wouldn't make any absolute statements. I can only make a guess at what it might be doing.

--------------------
Colt 45 - the original point and click interface

Lester Policarpio SSCertifiable Points: 7109 More actions · Answer 7

Anyways theres nothing wrong with it and it does not affect our database im just curious thanks a lot Philcart sorry for so many questions regarding the subject matter and again thank you for your patience. So you think this thing is normal and nothing to worry about??

"-=Still Learning=-"

Lester Policarpio