Updating a large table in sql server
I was informed this has the potential to fill up the transaction log . . . and it would be better to batch the updates


It would be better if it didn't fill up the transaction log.  But the proposed remedy is the wrong one.

You should size your transaction log to support your transactions, not the other way around.  


  Does the second approach yield any benefit in terms of the transaction log on large table updates?


Yes.  The transaction log can be reused between batches, so long as all the batches aren't in a transaction.


  increasing the disk space to support that would be troublesome 


Yes, sometimes you do have to code around space issues, but coding isn't free.  Spending money on infrastructure to reduce coding time is usually a wise move.

Also if you are trying to minimize log space, consider loading an empty table with your query, and then performing an ALTER TABLE … SWITCH.  Loading the new table can be minimally logged, and the ALTER TABLE is a metadata operation.

This will also enable you to perform the operation in a transaction, and not commit intermediate results.