Steen Schlüter Persson (DK),
You are right that it could lead to misinterpretation, so I am posting the
link to the BOL. I want to remark this part:
*****
You can re-create a whole database in one step by restoring the database
from a full database backup to any location. Enough of the transaction log
is included in the backup to let you recover the database to the time when
the backup finished. When the database is recovered, uncommitted
transactions are rolled back. The restored database matches the state of the
original database when the restored backup finished, minus any uncommitted
transactions.
*****
Full Database Backups
http://msdn2.microsoft.com/en-us/library/ms186289.aspx Thanks for your comment,
AMB
""Steen Schlüter Persson (DK)"" <steen@REMOVE_THIS_asavaenget.dk> wrote in
message news:eThesTXcHHA.648@TK2MSFTNGP04.phx.gbl...
[quoted text, click to view] > Alejandro Mesa wrote:
>> prince,
>>
>> Yes, It include transaction log backup but it does not truncate the log.
>> You need to backup the transaction log in order to truncate it (reuse
>> inactive part).
>>
>>
>
> I think it's a matter of interpretation to say that a FULL backup also
> include a Transaction Log backup..:-). The only part of the transaction
> log that's being backed up during a FULL database backup, is that part
> needed in order to recreate the log file during a restore and then the
> changes that has been done in the database between the start and end of
> the full backup.
> In general, I think it's more correct to say that a FULL backup doesn't
> backup the TLog.
>
> --
> Regards
> Steen Schlüter Persson
> Database Administrator / System Administrator