Correct UseDatabaseTransferQueue setting and remove from v13 and up

Author: ronaldbarendse

10/umbraco-deploy/getting-started/deploy-settings.md

@@ -48,7 +48,7 @@ For illustration purposes, the following structure represents the full set of op
             "DiskOperationsTimeout": "0.0:05:00",
             "SourceDeployBatchSize": null,
             "PackageBatchSize": null,
-            "UseDatabaseBackedTransferQueue": true,
+            "UseDatabaseTransferQueue": true,
             "IgnoreBrokenDependenciesBehavior": "Restore",
             "AcceptInvalidCertificates": false,
             "TransferFormsAsContent": true,
@@ -169,7 +169,7 @@ If encountering this issue, there are two batch settings that can be applied wit
 * `SourceDeployBatchSize` - applies a batch setting for the transfer of multiple selected items to an upstream environment (such as a media folder with many images).
 * `PackageBatchSize` - applies a batch setting to the processing of a Deploy "package", which contains all the items selected for a Deploy operation, plus all the determined dependencies and relations.
 
-## UseDatabaseBackedTransferQueue
+## UseDatabaseTransferQueue
 
 In earlier versions of Umbraco Deploy, the transfer queue was implemented using in-memory storage. As a result, it would not be persisted across application restarts.
 

13/umbraco-deploy/getting-started/deploy-settings.md

@@ -48,7 +48,6 @@ For illustration purposes, the following structure represents the full set of op
         "DiskOperationsTimeout": "0.0:05:00",
         "SourceDeployBatchSize": null,
         "PackageBatchSize": null,
-        "UseDatabaseBackedTransferQueue": true,
         "IgnoreBrokenDependenciesBehavior": "Restore",
         "AcceptInvalidCertificates": false,
         "TransferFormsAsContent": true,
@@ -189,14 +188,6 @@ If encountering this issue, there are two batch settings that can be applied wit
 * `SourceDeployBatchSize` - applies a batch setting for the transfer of multiple selected items to an upstream environment (such as a media folder with many images)
 * `PackageBatchSize` - applies a batch setting to the processing of a Deploy "package", which contains all the items selected for a Deploy operation, plus all the determined dependencies and relations
 
-### UseDatabaseBackedTransferQueue
-
-In earlier versions of Umbraco Deploy, the transfer queue was implemented using in-memory storage. As a result, it would not be persisted across application restarts.
-
-From 10.1, a database-backed queue was implemented and is used by default.
-
-If for any reason there was a need to revert to the previous implementation, the value of this setting can be set to `false`.
-
 ### TransferFormsAsContent {#transfer-forms-data-as-content}
 
 In order for Deploy to handle Forms data as content, you'll to ensure the `TransferFormsAsContent` setting is set to `true`. To transfer Forms data as schema, i.e. via .uda files committed to source control, use a value of `false`.

14/umbraco-deploy/getting-started/deploy-settings.md

@@ -49,7 +49,7 @@ For illustration purposes, the following structure represents the full set of op
         "SourceDeployBatchSize": null,
         "PackageBatchSize": null,
         "MaxRequestLength": null,
-        "UseDatabaseBackedTransferQueue": true,
+
         "IgnoreBrokenDependenciesBehavior": "Restore",
         "AcceptInvalidCertificates": false,
         "TransferFormsAsContent": true,
@@ -196,14 +196,6 @@ When Deploy transfers files between unconnected environments (like a non-public
 
 If no value is set, Deploy will create 16MB chunks, unless the [CMS `MaxRequestLength` setting](../../umbraco-cms/reference/configuration/runtimesettings.md) is lower (CMS setting is configured in kilobytes). Setting a value higher than the CMS `MaxRequestLength` (multiplied by 1024) will cause a validation error. Similarly, configuring a value higher than the [server or infrastructure limits](../../umbraco-cms/reference/configuration/maximumuploadsizesettings.md) will result in file transfers failures.
 
-### UseDatabaseBackedTransferQueue
-
-In earlier versions of Umbraco Deploy, the transfer queue was implemented using in-memory storage. As a result, it would not be persisted across application restarts.
-
-From 10.1, a database-backed queue was implemented and is used by default.
-
-If for any reason there was a need to revert to the previous implementation, the value of this setting can be set to `false`.
-
 ### TransferFormsAsContent {#transfer-forms-data-as-content}
 
 In order for Deploy to handle Forms data as content, you'll to ensure the `TransferFormsAsContent` setting is set to `true`. To transfer Forms data as schema, i.e. via .uda files committed to source control, use a value of `false`.

15/umbraco-deploy/getting-started/deploy-settings.md

@@ -49,7 +49,6 @@ For illustration purposes, the following structure represents the full set of op
         "SourceDeployBatchSize": null,
         "PackageBatchSize": null,
         "MaxRequestLength": null,
-        "UseDatabaseBackedTransferQueue": true,
         "IgnoreBrokenDependenciesBehavior": "Restore",
         "AcceptInvalidCertificates": false,
         "TransferFormsAsContent": true,
@@ -196,14 +195,6 @@ When Deploy transfers files between unconnected environments (like a non-public
 
 If no value is set, Deploy will create 16MB chunks, unless the [CMS `MaxRequestLength` setting](../../umbraco-cms/reference/configuration/runtimesettings.md) is lower (CMS setting is configured in kilobytes). Setting a value higher than the CMS `MaxRequestLength` (multiplied by 1024) will cause a validation error. Similarly, configuring a value higher than the [server or infrastructure limits](../../umbraco-cms/reference/configuration/maximumuploadsizesettings.md) will result in file transfers failures.
 
-### UseDatabaseBackedTransferQueue
-
-In earlier versions of Umbraco Deploy, the transfer queue was implemented using in-memory storage. As a result, it would not be persisted across application restarts.
-
-From 10.1, a database-backed queue was implemented and is used by default.
-
-If for any reason there was a need to revert to the previous implementation, the value of this setting can be set to `false`.
-
 ### TransferFormsAsContent {#transfer-forms-data-as-content}
 
 In order for Deploy to handle Forms data as content, you'll to ensure the `TransferFormsAsContent` setting is set to `true`. To transfer Forms data as schema, i.e. via .uda files committed to source control, use a value of `false`.