We are experiencing problems with full optimize + compress because our SQL transaction log is growing to the size of our disk (10Gig). We manually shrink the log file but as soon as we kick off an optimize it grows to 10G again in a matter of minutes. We're looking for some kind of configuration that will allow the optimization process to finish successfully without letting the log file grow so large. We have a simple recovery method set on our server. The result of the optimization failing has left all of our finance application record in the fact2 table instead of the fact table.
Can any one help.