Find and export
your Amazon Redshift data.

1. 1Connect through Query Editor or another SQL client with access to SVV_TABLE_INFO.
2. 2Run the read-only query below in each database in scope.
3. 3Convert the reported MB to GB and keep the schema breakdown.
4. 4Review business timestamps and row statistics separately to describe the retained history.

SELECT "schema", SUM(size) AS size_mb
FROM svv_table_info
GROUP BY "schema"
ORDER BY size_mb DESC;

Report in GB, naming databases, schemas and storage basis. Add row quantities and the principal table types where useful.

Use the earliest relevant business dates rather than only table-creation dates. Identify replicas or archive copies separately.

1. 1Have the administrator confirm an approved S3 destination and the required data and storage permissions.
2. 2Use UNLOAD for the selected tables or queries, choosing Parquet or another suitable supported format.
3. 3Include a manifest when useful and collect every output file.
4. 4Preserve schemas and validate table or row coverage against the inventory.

UNLOAD writes parallel output files. Format support differs for some column types, so inspect the schema before exporting.

The operation uses the selected warehouse resources and destination storage. Review scope and applicable costs with the administrator.

Warehouse tables can connect operational events from several business systems.

Schema and date context helps explain the steps represented by those records.

Select databases, tables and columns in scope, reviewing personal fields and confidential analytical material.

Telegraph Lab reviews the proposed material with you and agrees how sensitive information will be handled. Preparation can include excluding material, redacting details and replacing personal identifiers. Your company keeps ownership; the licensing agreement defines the material, permitted uses and authorized recipients.