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 |
|
keithc1
Yak Posting Veteran
88 Posts |
 Posted - 2004-06-23 : 10:50:11
|
| Hey all I need like an explanation of what is going on more than anything.I have a table with 100,000 + rows, I did a Delete from table since the data is unimportant and am just learning.I had maxsize originaly set on the transaction log so this delete failed. After i set to unlimited I went into QA reran the DELETE from table and watched the tran log auto grow within EM.The delete worked now and the transaction log is now 500 megs bigger than its originaly specified max size which coincidently was also 500 meg.Now I look in EM and the used portion is 10 meg and free space is now like 940meg.My questions are1) what if i want to rollback the delete i just did, i thought the transaction log would be full of used space after the above operationI do have Simple Recovery specified on this DB so is that the reason why i have so much free space in the tran log now?2)will the transaction log stay the size that it auto grew to until i execute an operation that forces it to auto grow more?Keithc MCSE MCSA |
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2004-06-23 : 11:44:09
|
| You need to shrink the transaction log, to do this, just run a backup and it should shrink it... It has grow to this level as that was the space it needed to do the delete (delete creates transactions as it may need to rollback)... If you want to clear out a table without any logging, use truncate table...The answer to question 1 is, depends on if you are doing transaction log backups, which you obviously aren't as you have the recovery mode set to simple... |
 |
|
|
|
|
|
doing a large row delete