Skip to main content

Exporting Legacy Metadata

Analyzer expects all the legacy code to be exported into a folder accessible by it.
For SQL code exporting, most times a database export can be used to export object definitions (tables, views procedures, functions etc...) in bulk. Ideally, each SQL file should contain a single artifact.

All the major ETL platforms provide some kind of export of their code repositories. Typically this is done into XML or JSON formats which can be used to restore the environment. Here is a short guide for how to export metadata from various platforms:

Microsoft SQL Server​

To extract metadata like Table, View, and Stored Procedures DDLs, you can use Microsoft SQL Server Management Studio (SSMS).

  • In Object Explorer, expand the node for the instance containing the database to be scripted.
  • Right-click on the database you want to script, and select Tasks > Generate Scripts. sql-server-export-object-explorer
  • On the Choose Objects dialog page, select either the entire database or choose the object types to be migrated.
    • Note: Select all required object types. Screenshot below is for illustration purposes only.
    sql-server-export-choose-objects
  • In the Set Scripting Options dialog page, choose Save as script file and one script file per object as illustrated below.
    sql-server-export-set-scripting-options

See https://learn.microsoft.com/en-us/ssms/scripting/generate-and-publish-scripts-wizard for more details on how to use the Generate Scripts wizard in SSMS.

Azure Synapse (Dedicated)​

Follow the same steps as for Microsoft SQL Server above. The only difference is that you will need to connect to the Synapse Dedicated SQL pool instead of a regular SQL Server instance.

Azure Synapse (Serverless)​

If you use Synapse Studio and have your SQL code saved in SQL scripts, you can export the files with the Export-AzSynapseSqlScript PowerShell cmdlet. This method requires Azure PowerShell modules.

Otherwise, you can use Microsoft SQL Server Management Studio (SSMS) to extract metadata like Table, View, and Stored Procedures DDLs.

  • Select “Object Explorer Details” under the View button in the toolbar synapse-objects-explorer-view
  • For each object type, select the required objects to export and right-click on the selection to choose “Script as” > “CREATE To” > “File” as pictured below.
    synapse-objects-explorer-script-as

DataStage​

  • Typically in DataStage the easiest way to export the objects is by using the GUI. However, Datastage has command line utilities to export via CLI.
  • Please use the XML format, as both Analyzer and Converter support XML-only Datastage exports

SSIS​

You’ll need to export the DTSX packages. For details on how to obtain it see: https://docs.microsoft.com/en-us/sql/integration-services/import-export-data/save-and-run-package-sql-server-import-and-export-wizard?view=sql-server-ver15

In many cases the DTSX packages can also be just copied to the analyzer folder.

Talend​

To export all jobs in bulk, right click on Job Designs and select "Export Items". In the popup, select "Include All Dependencies"

talend-export

Note: while Talend jobs can be exported as a single zip file, when running analyzer or any converter utilities please unzip the file(s). Both the analyzer and converters will look for .item and .properties files in non-zipped folders.

ODI​

Exporting jobs in ODI is detailed in this document: https://docs.oracle.com/middleware/1212/odi/ODIDG/export_import.htm#ODIDG578

Alteryx​

Analyzer needs the .yxmd files. These can be obtained by Select File > Export to download your workflow to your local machine in .yxmd format.

SAP Business Objects Data Services​

Instructions for export can be found in the following articles: https://help.sap.com/viewer/2d2abbb0fab34071a4c53b7de873241b/4.2.13/en-US/571901366d6d1014b3fc9283b0e91070.html https://help.sap.com/viewer/2d2abbb0fab34071a4c53b7de873241b/4.2.13/en-US/5718d4ba6d6d1014b3fc9283b0e91070.html