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
  • Core emulation concepts
  • Emulation necessity and scope
  • Supported emulation scenarios
  1. Emulation Scenarios

Emulation in SQL Tran

Core emulation concepts

In the context of SQL Tran, emulation refers to the intelligent rewriting of SQL code from one database platform to another, preserving the original business logic even when direct translation is not possible.

Rather than simply copying syntax, SQL Tran adapts the code to fit the architectural and functional realities of the target system, ensuring compatibility and operational correctness.

Emulation often involves restructuring SQL constructs, replacing unsupported features with equivalent logic, and adjusting for differences such as data type behavior, transaction handling, and execution environment.


Emulation necessity and scope

Migrating databases between fundamentally different systems — for example, from a traditional SQL Server installation to a massively distributed Fabric Warehouse — is not simply a matter of rewording statements.

Differences in storage architecture, processing models, SQL dialects, and feature sets mean that some constructs must be rewritten entirely to preserve their intended behavior.

Without emulation:

  • Key functionality could break or produce incorrect results.

  • Applications depending on database logic might fail.

  • Migration projects would require massive manual effort, increasing cost and risk.

SQL Tran automates much of this emulation process, significantly reducing manual work and ensuring that migrations are faster, safer, and more reliable.


Supported emulation scenarios

SQL Tran currently supports emulation for the following source-target migration scenarios:

Source

Target

Details

SQL Server

Fabric Warehouse

Synapse Analytics

Fabric Warehouse

SQL Server

Synapse Analytics

Oracle

PostgreSQL

(Note: More source and target combinations are currently in development and will be added in future updates.)

Each scenario comes with its own challenges based on the specific differences between the platforms involved. SQL Tran provides scenario-specific emulation techniques to ensure the highest possible translation accuracy. These are illustrated with code examples and clearly noted limitations where manual adjustments may be required.

PreviousPrerequisites for Azure Marketplace deploymentNextSQL Server to Fabric Warehouse

Last updated 4 days ago

See section:

See section:

See section:

See section:

SQL Server to Fabric Warehouse
Synapse Analytics to Fabric Warehouse
SQL Server to Synapse Analytics
Oracle to PostgreSQL