There does need to be enough physical space for the log file and it does need to be allowed to grow. Normally in a SQl Server set up the Log File will be set to autogrowth with maxsize set to unlimited, but if there isn't enough physical space then this will not help. The second thing is that providing the recovery model is set to simple (which it will in a standard install) then running a backup will truncate the logfile. If you can run the R6 database backup before making large changes (eg a dictionary upgrade, or bulk delete) this will clear the logfile leaving as much space as possible for the process.
My feeling will be that IT departments will not normally have changed the recovery model from 'simple'. They may have modified the autogrowth options, and they may also be limiting the physical space available. If so a backup will make best use of the space available, but there may still not be enough in some situations, In which case the growth options will need changing and if required more the physical space made available.
The SQL at https://forums.nbn.org.uk/viewtopic.php?id=7478 will reset the recovery model to simple if it has been changed and clear the logfile. The log file growth options can be found and changed in Management Studio by right clicking on the database (NBNData) choosing properties, then files. The current log file properties can be seen and changed here.
Littlefield Consultancy - IT Consultants