HoarderServiceClient.ExportToTsvNormalised Method

public Task<string> ExportToTsvNormalised()

Return Value

This call starts the export processing running in the background then returns. The response body string contains the Uri of the Azure Blob that will containing the processing log when the export completes. The whole database is exported in 3rd normal form to a set of tab delimited text files in the backup container. Each file represents a normalised RDB table. The files can be imported directly into a SQL Server database very slowly by a utility command elsewhere in the solution. Each file could theoretically construct an RDB holding the collection. Blog post Collections Database History (https://gfkeogh.blogspot.com/2018/01/collections-database-history.html) discusses how the old Agate SQL Server database was denormalised to create the Hoarder Cosmos database, so this method is ironically the reverse process. It's all an academic exercise. The set of exported files is first created in subfolder of the data folder specified in the Hoarder configuration, then each of those files is uploaded to a contain and virtual directory also specified in the Hoarder configuration.

Reference