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 |
|
mbevon
Starting Member
41 Posts |
 Posted - 2002-08-28 : 09:25:15
|
| How could i truncate the transaction log?How could i stop the database from dong a transaction log backup?thanksMarls |
|
|
rihardh
Constraint Violating Yak Guru
307 Posts |
Posted - 2002-08-28 : 10:06:52
|
| Hi!My first question is:"Why are you asking this question?"My second question is :"Do you know what BOL means?"My third question is :"Did you browse the older forum topics?"If you successfuly answered all of the questions above, take this advice: "Don't jump headon into the water unless you know how deep it is!!!" |
 |
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-08-28 : 10:12:12
|
| Backing up transaction log truncates it.If you aren't planning to use your log backups in your database recovery, you can execute BACKUP LOG dbname WITH NO_LOG. If you need to reduce the size of the log file after the log has been truncated, you can execute DBCC SHRINKFILE. The log doesn't get backed up by itself... There must be a job/maintenance plan that performs this backup. So if you want to stop the log from being backed up you can remove that job/maintenance plan. But since the logs won't get truncated if you stop log backups, you would probably want to change the recovery mode of your database to 'simple'(SQL2k) or set 'trunc. log on chkpt' option to true (SQL7) to prevent log file from getting too big. |
|
|
|
|
|
|
Transaction Log