During the development of SQL Backup, we found that it made very little difference in backup throughput when bumping up the buffer size from 1 MB to 4 MB, but it increased the memory requirements fourfold.
We also found out that errors sometimes occur when during a restore, a MAXTRANSFERSIZE value that's different from the value used during the backup is used. Thus, to avoid situations where the secondary server cannot meet the memory requirements and fail to restore the backup, we decided to limit the MAXTRANSFERSIZE to a conservative 1 MB.
Could you please post the link to the article you mentioned?
SQL Backup Consultant Developer
Associate, Yohz SoftwareBeyond compression
- SQL Backup goodies under the hood, updated for version 8