Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
alif
Starting Member
2 Posts |
 Posted - 2006-04-11 : 08:55:16
|
| Hi is it possible to execute the commandBACKUP LOG <database name> WITH TRUNCATE_ONLYduring normal operation of the database : when users are working actively on the database.is a risk to corrupt the database or the only risk is the lost of some transactional logs.Please helpThank you |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-04-11 : 11:47:41
|
| It shouldn't corrupt the database.If you are doing this why not set it to the simple recovery model?seehttp://www.nigelrivett.net/SQLAdmin/TransactionLogFileGrows_1.html==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
ravilobo
Master Smack Fu Yak Hacker
1184 Posts |
Posted - 2006-04-11 : 11:58:03
|
| If the DB is small then go for SIMPLE recovery model (as suggested by nr) and daily FULL backup.------------------------I think, therefore I am - Rene Descartes |
|
|
|
bakerjon
Posting Yak Master
145 Posts |
Posted - 2006-04-11 : 13:38:34
|
| Of course, if you want to recover transactions to a point in time, it is a good idea to have it in FULL recovery. It might be OK to change recovery model to get yourself out of a jam, but you will want to switch to FULL recovery and take a full backup if you want real protectionJonHolding it down on the engineering tip, y'all!http://www.sqljunkies.com/weblog/outerjoin |
|
|
|
alif
Starting Member
2 Posts |
Posted - 2006-04-12 : 22:08:38
|
| Thanks to all,I ran out of disk space. that's why I truncated the logfile.After that I shrunk the log file to free some space.Thanks, |
|
|
|
|
|
|
BACKUP LOG suring normal operations