does 'backup log... truncate_only' post all transactions to the mdb

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Roger - 09 Jul 2008 10:26 GMT

backup log db with truncate_only
DBCC SHRINKFILE (db_log, 100) WITH NO_INFOMSGS
backup database db to disk = 'd:\backup\db.bak' with init

does the 'backup log' statement flush all transactions to the db
database ?
and is does the same happens whether it's a 'truncate_only' or 'to a
disk file' ?

assuming no further activity, does the 'backup database' statement
cause all my data to be backed up ?

is it prudent to schedule "backup log db to disk = 'd:\backup\db.trn'
with init" throughout the day, say every hour ?

if so, how can I programatically name the disk file, ie db_1.trn,
db_2.trn, etc ?
or do I just overwrite db_trn ?

Reply to this Message

Uri Dimant - 09 Jul 2008 12:22 GMT

Roger

> backup log db with truncate_only
> DBCC SHRINKFILE (db_log, 100) WITH NO_INFOMSGS
> backup database db to disk = 'd:\backup\db.bak' with init

Read Tibor's article , I'd just add that when you backup log file sql
server just writes all committed transactions to the disk to make virtual
logs ( log file contains /built virtual logs) to be reused ( keep physical
size fo the log)

http://www.karaszi.com/SQLServer/info_restore_no_truncate.asp
http://www.karaszi.com/SQLServer/info_dont_shrink.asp

> is it prudent to schedule "backup log db to disk = 'd:\backup\db.trn'
> with init" throughout the day, say every hour ?

I usually do backup log files with not init option as the .bak contains
fileid to be refernce in restore

> if so, how can I programatically name the disk file, ie db_1.trn,
> db_2.trn, etc ?
> or do I just overwrite db_trn ?

Again Tibor has pretty good examples on his site

> backup log db with truncate_only
> DBCC SHRINKFILE (db_log, 100) WITH NO_INFOMSGS
[quoted text clipped - 14 lines]
> db_2.trn, etc ?
> or do I just overwrite db_trn ?

Reply to this Message