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 |
|
catparks
Starting Member
18 Posts |
Posted - 2002-01-22 : 12:32:53
|
Truncating & shrinking the log file in SQL 2000 seems to be more difficult than in version 7.0. I would like to know the best (and easiest) way to regularly truncate and shrink the log file. So far, I haven't found a decisive answer to that question. Any suggestions? My log files just keep growing and growing... |
|
|
KnooKie
Aged Yak Warrior
623 Posts |
Posted - 2002-01-22 : 12:52:28
|
| search this forum, there are probably loads of posts covering this topic as truncating the log seems to cause lots of problems for people. |
 |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2002-01-22 : 12:54:09
|
| Best to make sure they don't get bis in the first place by making sure you have small transactions and a reasonable backup strategy.I always shrink log by detaching the database, removing the log and attaching the database (after a backup of course).You can shrink the log but this often takes a few attempts.==========================================Cursors are useful if you don't know sql.Beer is not cold and it isn't fizzy. |
 |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-01-22 : 13:40:55
|
| What is easier about 7.0? Are you refering to there being no 'truncate log on checkpoint' option? If so, simple recovery mode is the same as having 'truncate log on checkpoint' selected in 7.0.-Chad |
 |
|
|
|
|
|