The message is a warning that your database is using the Full recovery
model, but you have truncated the log and so it will not be possible to
recover to a point in time, or following a system failure - you will have to
load your last full backup, and any changes after that are lost.
If I understand your description correctly, you do a full backup every
night, but no transaction log backups during the day. If so, you might
consider putting the database in the Simple recovery model, which means the
log will not grow so large, and you will not see these warning messages. The
disadvantage is that if the system fails, you will lose all modifications
since the last full backup, but it looks like you don't want or need fuller
recovery anyway.
The BOL topic "Selecting a Recovery Model" has a good explanation of the
differences between the various recovery models.
Simon
"A.M. de Jong" <ar****@wxs.nl> wrote in message
news:bd**********@reader08.wxs.nl...
Hi,
Every day we perform a full database backup.
(during the night).
Since we need no "additional" backups we had the problem that the
transaction log file grows and grows.
Therefore now just after the backup we perform a backup of the transaction
log with no log.
So we free up the space in the log file. (it truncates).
However, now we get this errormessage:
PRB: A "Database log truncated" Error is Logged in the Event Log When You
Try to Back Up the Transaction Log
http://support.microsoft.com/default...en-us%3b818202
I am aware of this message but I think that it is basically a warning.
Am I correct ???
Arno de Jong, The Netherlands.
