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 |
|
dr_seusse
Starting Member
22 Posts |
 Posted - 2002-07-18 : 09:50:39
|
| What happens when one of my log files gets to large?How can I reduce the size if possible?cheers |
|
|
M.E.
Aged Yak Warrior
539 Posts |
Posted - 2002-07-18 : 09:57:54
|
| back it up with or without full truncate.-----------------------Take my advice, I dare ya |
 |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-07-18 : 12:38:58
|
| That will not shrink it. You need to use 'dbcc shrinkfile' after truncating. look it up in BOL.-Chad |
|
|
|
dr_seusse
Starting Member
22 Posts |
Posted - 2002-07-19 : 09:41:09
|
| First off, I'm getting error "status=112, see SQL Server Log" while trying to back up my log file.Where do I go to see my SQL Server Log?Which file do I select to "backup to"?the ProjectName.bak file correct?Where do I find the 'with or without full truncate' option? I've tried to append to media & overwrite existing media. Both give me the above error.Thanks |
|
|
|
dr_seusse
Starting Member
22 Posts |
Posted - 2002-07-19 : 10:04:44
|
I have not yet solved my previous problem, but regarding chadmat's suggestion...My log file is currently nearly 7 GB. I've read the different shrinking options on BOL, but am still hesistant/unsure. Should I just use the TRUNCATEONLY option, since i don't really have a grasp of what size i'd like to shrink the file to.Furthermore, where would I perform the statement below (and is the syntax correct)? Query Analyzer?---USE ProjectNameDBGODBCC SHRINKFILE (1071410, TRUNCATEONLY)GOThanks again  Cheers! |
|
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2002-07-19 : 11:45:54
|
| Don't do anything, until you are very sure of what you are doing. Go back to Books Online or your other resources and keep reading until you understand how the transaction logs.<O> |
|
|
|
|
|
|
log file getting HUGE