Reading from the data files - you can test this by doing a backup to NUL:, as in this example, which won't break your log-backup chain for full recovery model databases: BACKUP DATABASE xyz TO DISK = 'NUL:' WITH COPY_ONLY Ĭompressing the data - watch CPU pressure during the backup. The parameters are the folder path where you want to move files from and the folder path where you want to move files to.There's basically 4 things involved with backup speed: Select Debug, enter the Parameters, and then select Finish. You'll see the pipeline, as in the following example: Select existing connection or create a New connection to your destination file store where you want to move files to.
Be aware that DataSource_Folder and DataSource_File are reference to the same connection of your source file store. Select existing connection or create a New connection to your source file store where you want to move files from.
This article describes a solution template as another approach leveraging ADF flexible control flow plus copy activity and delete activity to achieve the same scenario. By doing so, copy activity will delete files from data source store after job completion. The way to enable it is to set “deleteFilesAfterCompletion” as true in copy activity. ADF copy activity has built-in support on “move” scenario when copying binary files between storage stores.