sql transaction log has not been updated for 30 days

We have a SQL database that the last update date to the transaction log is 30 days ago.  it is set to autogrow and is no where near full size.  Actually, it is quite small compared to the database.  we have had no performance issues but this concerns me.  I am at a loss to how this can happen.

Thank you,
BUCKBERGAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott PletcherSenior DBACommented:
Are you going by the directory "last updated" date?  That is not necessarily accurate for SQL Server files.  SQL doesn't update the date every time it writes (good thing, as the overhead of that would be enormous).
0
rhandelsCommented:
The transaction log will only grow if you have the full recovery model activated.
Also, if you have full recovery model enabled the transaction log will be truncated if you do a full backup of the database or a translog log backup.

So normally your transaction log should be smaller than your database, it will only be larger than your database if you have a rather small database with a large amount of changes to the database.
0
Scott PletcherSenior DBACommented:
>> The transaction log will only grow if you have the full recovery model activated. <<

False.  Logging occurs in any recovery model when any type of data modification is done.


>> Also, if you have full recovery model enabled the transaction log will be truncated if you do a full backup of the database <<

False.  Backing up the database will not cause log truncation in that case, only a log backup does that, and only if the log records are not needed for any other purpose (replication, etc.).
0
BUCKBERGAuthor Commented:
Unfortunately, for the database the backup mode is "Copy Only".  I would suspect since there is no checkpoint that the transaction log would grow large, which is the experience I have with another instance at our sister site. The log file is tiny compared to database.  I will have to check if the recovery mode is simple. I am looking for another explanation.
0
Scott PletcherSenior DBACommented:
The database log will likely grow a lot less if it's in Simple recovery model, but the log can still grow, as logging does still occur.  The difference is that the log will be automatically truncated at checkpoint in simple mode (unless the log records are needed for some other purpose such as replication).  That allows existing log space to be used over and over rather than having to use additional log space until a log backup is done in full/bulk-logged mode.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

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.