You can change your recovery model as Allen already
suggested which will truncate your log on checkpoints.
However, there is no way to completely turn off logging
transactions to the transaction log.
An alter table doesn't usually hit too hard if you are
adding a nullable column which I would guess isn't the case
for you. To reduce the overhead, make sure not to do this
through Enterprise Manager. You may possibly be able to
reduce problems with your transaction log by allowing
minimally logged operations by setting your recover model to
Bulk-logged (or select into/bulk insert in 7.0) . Then do a
select into to create the table with the column definitions
you need. But this doesn't account for managing relationship
issues or the extra space needed in your data file. Just a
possible option depending on your situation.
On Thu, 28 Mar 2002 07:36:25 -0800, "Jeffrey Bradshaw"
>I've got a large table that we need to add a column to.
>When doing the alter table command, the transaction log
>fills up and we run out of space. We have turned on auto
>grow in the log but we run out of physical disk space.
>Is there any way to temporarily turn off the transaction
>logging? Essentially I want to do an alter table just like
>truncate table in that nothing is save. I realize there's
>a potential for problems if the server crashes or dies
>during the operation.
>Any help would be appreciated.
>TIA - Jeffrey.