Transaction log during index defrag

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hello everyone,

Index reorgs are an important aspect of keeping your database healthy
and running smoothly. Depending on the indexes being reorged, however,
a reindex or defrag can use significant amounts of log space which is
why I've always done reorgs manually. I have a job that will backup the
transaction log when it gets to a certain percentage used, but it still
needs babysitting during the reorg as I occasionally run into "log is
full errors". I thought about setting the transaction logs to
automatically grow and shrink as needed, but I'm concerned that would
cause further disk fragmentation at the OS level. I could make the
transaction log very large in size, but I'm not sure if that's the way
to go either. I could also lower the threshold on the job to something
like 25% which might help. How do other people handle this? I'm wanting
to get out of the babysitting business!

Thanks,
Aaron

.