SQL Export in TimeXtender Deliver Instance

Hi ​@Paul McLeod Bespoke Analytics ,

what are your requirements here - as there are a great many ways of achieving this. The old functionality pushes .bak if I remember correctly? Even that could be done from SQL or through Powershell currently (Backup-SqlDatabase (SQLServer) - SQL Server PowerShell | Microsoft Learn), but it would be beneficial to add the feature in TDI.

In other scenarios you might want to set up some kind of replication from your main MDW database to a target database elsewhere. In the new release you could either add an instance (but there is no Prepare → Prepare data movement possible right now so would need the existing objects setup with security at the schema level) or set up the replication at the infrastructural level. If you are pushing the whole MDW, you can use the easy setup of read-only replica’s in Hyperscale for instance. 

We have some setups in 20.10.x where we add another MDW-like database that gets some of the content of the full MDW where the new database is actually hosted at a 3rd-party we push the data to.

I have the ability to perform Data Movements from one Prepare to another Prepare included in this Idea: Make instances and data areas more consistent | Community

Please add option for (Delta) Parquet format in Data Export as well. And add option to store the CSV/Parquet on a Azure Blob/Storage container.