SQL Tran Docs
  • Overview
    • About
    • Getting started
    • Object lifecycle
    • Why is there no AI inside?
    • Performance considerations
    • Security considerations
    • Assessment
    • Unlocking projects
    • Interface walk-through
    • Translation scenarios
    • Prerequisites for Azure Marketplace deployment
  • Emulation Scenarios
    • Emulation in SQL Tran
    • SQL Server to Fabric Warehouse
      • Data types
      • Case sensitivity
      • Cursors
        • Basic cursor loop
        • Cursor types
        • Fetch direction modes
        • Cursors in control flow
        • Nested cursors
        • Data modification cursors
        • Multiple cursors
        • Subqueries and filtering
      • Named procedure parameters
      • Result set limiting
      • MERGE statements
      • Computed columns
      • External tables
      • Materialized views
      • Identity columns
      • Unsupported system objects
    • Synapse Analytics to Fabric Warehouse
      • Emulations
      • Limitations
    • SQL Server to Synapse Analytics
    • Oracle to PostgreSQL
  • Project wizard
    • Source database
    • Target database
    • Wrapping up
  • Projects
    • Project list
    • Overview
    • Workspace
    • Reports
    • Tests
    • Scratch pad
    • Settings
      • Project name
      • Mapping
      • Database connections
    • Navigation
    • Object complexity
    • Static analysis
    • Translation errors
    • Exporting and importing projects
  • Workspace
    • Object tree
    • Data lineage
    • Code
    • Actions
      • Overriding source
      • Overriding target
      • Ignoring objects
  • Tests
    • Workflow
    • Configure SQL Tran
    • Connecting to databases
      • Fabric Warehouse
      • Synapse Dedicated SQL Pool
      • Azure SQL Database, Azure SQL Managed Instance, Microsoft SQL Server
    • Tables
    • Views
    • Procedures
    • Functions
    • Triggers
    • Performance tests
  • Scripter
    • About
    • Supported databases
    • SQL Server
    • Azure SQL
    • Synapse Dedicated Pool
    • Oracle
    • PostgreSQL
    • MySQL
Powered by GitBook
On this page
  • Populating object scripts
  • Scripter tool
  1. Project wizard

Source database

PreviousOracle to PostgreSQLNextTarget database

Last updated 5 months ago

SQL Tran currently supports the following databases you can migrate from:

  • SQL Server

  • Synapse Dedicated Pool

  • Azure SQL Database

We are now working on adding the support for the Oracle source.

SQL Tran does not need to connect to your database. It only needs your code, or more specifically, it needs CREATE scripts of your tables, views, procedures, functions, and triggers.

Populating object scripts

SQL script file

If you have ready SQL script dump of your database, you can upload it. SQL Tran can handle huge scripts, but we have limited the file size to 100MB just to sanitize what users are able to do. That said, 100MB should get you some 1.5 million lines of code, which is quite substantial.

ZIP archive file

You can also upload a ZIP file containing your scripts. We will optimize import based on the ZIP file contents.

  • If all you have is a bunch of files, we will treat this as a single SQL script and concatenate all files before parsing.

  • If you have files placed into a correct folder structure where each folder represents object types, we will directly map each file into a database object. This is the preferred way to import scripts.

Folder structure

If you will be creating the ZIP archive manually, as opposed to using our Scripter tool, please make sure to use the following directory structure:

  • Types

  • Tables

  • Procedures

  • Views

  • Triggers

Each file should be named as the object whose script it contains.

Scripter tool

Scripting large and complex databases using existing tools can be challenging, which is why we built a single-exe tool to do it for you.

Scripter is a very simple console application which is able to generate either SQL or ZIP file containing all of your database metadata.

When you run it, Scripter will not connect to any servers. You can examine the generated file to ensure nothing sensitive is sent to SQL Tran servers.