Option MaxTransferSize for database backup commands should be an sp_configure option. - by Azhar Taj

Status : 

  Duplicate<br /><br />
		This item appears to be a duplicate of another existing Connect or internal item.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 837450 Comments
Status Resolved Workarounds
Type Suggestion Repros 0
Opened 3/20/2014 11:06:07 AM
Access Restriction Public


MaxTransferSize is by default set to 1 MB. At Microsoft IT we have found out that our storage arrays work with a lot less stress if MaxTransferSize is set to 256 KB. That is the recommended setting for many storage array vendors. We are currently going through this huge activity where backup jobs are being modified to add MaxTransferSize in there. If this were available as a SQL server wide option with sp_configure, it will make it so much easier for people to tweak it based upon what is appropriate for their environment.
Also, currently as per our conversation with SQL Dev, there is no way to specify MaxTransferSize for transaction log backups happening with LogShipping jobs and also any backup jobs happening via maintenance plans. Again, a server wide option would help resolve this.
Sign in to post a comment.
Posted by Azhar Taj on 7/24/2014 at 10:53 AM
I see this issue has been closed as a "Won't fix". Can we have some reasons provided to us as to why this item is not worth considering? Thanks!