|
|
Truncating the transaction log |
|
Author |
Message |
danny159
|
Posted: Mon May 21 05:47:01 CDT 2007 |
Top |
SQL Server >> Truncating the transaction log
Hi all,
Can anyone tell me if performing a full backup of a database should
truncate the transaction log? I perform full backups every night (with
no transaction log backups) but the transaction log still seems to grow
every day.
As I understand it, if a full backup does truncate the log the
transaction log should perhaps "peak" when the db is very busy but not
necessarily continue to grow at a uniform daily rate?
Many thanks to anyone who can advise
Kindest Regards
Simon
SQL Server97
|
|
|
|
|
Shama
|
Posted: Mon May 21 05:47:01 CDT 2007 |
Top |
SQL Server >> Truncating the transaction log
Hi,
No
If the database recovery model is other than simple,you need to perform
trn.log backup to truncate.
even if it grows beceause of various reasons ,we need to truncate and shrink
log file.
> Hi all,
>
> Can anyone tell me if performing a full backup of a database should
> truncate the transaction log? I perform full backups every night (with
> no transaction log backups) but the transaction log still seems to grow
> every day.
>
> As I understand it, if a full backup does truncate the log the
> transaction log should perhaps "peak" when the db is very busy but not
> necessarily continue to grow at a uniform daily rate?
>
> Many thanks to anyone who can advise
>
> Kindest Regards
>
> Simon
>
|
|
|
|
|
GilbertoZampatti
|
Posted: Mon May 21 05:50:00 CDT 2007 |
Top |
SQL Server >> Truncating the transaction log
The trucation of a log after a full backup is provided just in "Simple"
recovery model, not in "Full" or "Bulk-logged" recovery model.
To see and/or change the recovery model look at the Properties of your
database.
However if your model was "Full" or "Bulk-logged" you cannot obtain the
truncation just changing it: you should back up you database and then
manually shrink the log.
The subsequent backup will truncate your log (without change his
dimension!), freeing inner space for subsequent transactions.
Gilberto Zampatti
> Hi all,
>
> Can anyone tell me if performing a full backup of a database should
> truncate the transaction log? I perform full backups every night (with
> no transaction log backups) but the transaction log still seems to grow
> every day.
>
> As I understand it, if a full backup does truncate the log the
> transaction log should perhaps "peak" when the db is very busy but not
> necessarily continue to grow at a uniform daily rate?
>
> Many thanks to anyone who can advise
>
> Kindest Regards
>
> Simon
>
|
|
|
|
|
vt
|
Posted: Mon May 21 05:52:43 CDT 2007 |
Top |
SQL Server >> Truncating the transaction log
Hi Simon,
Full backup will not reduce the size of transaction log file, its a
sequential access file, it truncate the inactive portion of transaction log
file.
if you need to reduce the size of the transaction log file shirk it
use EM or dbcc shrinkfile
for more information on how transactional log works read sql server
administration book by Microsoft, i don't remember the exact title of it
--
VT
Knowledge is power, share it....
http://oneplace4sql.blogspot.com/
> Hi all,
>
> Can anyone tell me if performing a full backup of a database should
> truncate the transaction log? I perform full backups every night (with no
> transaction log backups) but the transaction log still seems to grow every
> day.
>
> As I understand it, if a full backup does truncate the log the transaction
> log should perhaps "peak" when the db is very busy but not necessarily
> continue to grow at a uniform daily rate?
>
> Many thanks to anyone who can advise
>
> Kindest Regards
>
> Simon
|
|
|
|
|
Simon
|
Posted: Tue May 22 05:57:33 CDT 2007 |
Top |
SQL Server >> Truncating the transaction log
Thanks guys
:-)
|
|
|
|
|
|
|