The same command you specified in your initial post works fine. Monitor on a regular basis for a couple of weeks, see how big the log needs to be, then you know how large the log needs to be.
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass