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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-01-30 : 08:20:17
|
| speno writes "I have a database that is being replicated every night from AS/400 files in SQL. As part of the DTS, the data in the tables is deleted then appended. This causes the transaction log file to grow quickly which is soon to cause more problems. Two questions. 1.How can I avoid the log file from growing so quickly? Restricting the file growth caused the backup not to complete b/c the transaction log was full. 2.Since this is a replicated database where backups aren't needed, is it possible to not use the transaction log at all?tks" |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-01-30 : 13:33:14
|
| You could truncate the log imediately after the DTS Package runs (That is if you don't use T-Log Backups, if you do, ignore this suggestion). Then run a DBCC Shrinkfile to get it back to the size you want it.What type of Replication are you using? If you use snapshot, you could truncate the table before importing (That is minimally logged).HTH-Chad |
 |
|
|
|
|
|
Restrict transaction log file