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 |
|
radha
Starting Member
11 Posts |
 Posted - 2004-10-11 : 03:14:35
|
| Transaction Log file saved in F: drive.That F: drive is full because og Transaction LOg.How to resole this problem |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-10-11 : 04:21:43
|
| is the transaction log any significance to you? if not then you can issue a1. backup log with truncate_only2. dbcc shrinkfile 'logfile'but this will only remedy what you are encountering right now, you should plan a backup system for your databases. |
 |
|
|
sify
Starting Member
18 Posts |
Posted - 2004-10-12 : 02:25:39
|
| Check the current option for the database. If the database is in Simple recovery Mode(Trunc log on chkpt.) then there must be an open transaction running. You might need to kill that process before truncating the log and shrinkging the log file |
|
|
|
hgorijal
Constraint Violating Yak Guru
277 Posts |
Posted - 2004-10-12 : 05:20:13
|
| ..by "backup system", I'm sure Jen meant a Backup Strategy.If you already have backup strategy that truncates the log after a full back, you might also want to move the log file to a bigger drive and/or analyse what is causing the log to grow that big.Hemanth GorijalaBI Architect / DBA... |
|
|
|
|
|
|
Transation Log File!