When using the Sitecore Azure module to deploy the Sitecore database, the deployment process may fail with the following error message when the size of the deployed database is large (more than 2 GB):
A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
At the same time, an exception with the following message would be added to the Windows Azure SQL Database logs:
The session has been terminated because of excessive transaction log space usage. Try modifying fewer rows in a single transaction.
This is because Sitecore Azure does not split the data into parts while deploying databases. Thus, in case of large amount of data, the mentioned errors may appear due to the excessive usage of the transaction log.
This issue affects Sitecore Azure 2.0 - 7.2 versions.
To resolve the issue, download and extract the corresponding archive into the /Website folder of your website:
In Sitecore Azure 7.5, a new setting controlling the number of database rows per transaction was introduced:
<setting name="Azure.BulkCopyBatchSize" value="0" />
It is disabled by default. If the database deployment fails because of the transaction log space limit, open the Sitecore.Azure.config file and change the value of this setting to "500".