Case sensitivity emulation

Synapse Analytics typically operates in a case-insensitive environment, allowing object names to be referenced in any casing without issue.

However, Microsoft Fabric Warehouse is case-sensitive by default, meaning that differences in letter casing create distinct objects. Inconsistent casing — harmless in Synapse — can lead to runtime errors in Fabric if not properly handled.

SQL Tran automatically addresses this by analyzing the SQL structure and adjusting identifier casing across all usage points. Object names are normalized to match their original definitions, and aliases are rewritten to align with Fabric’s conventions.

This automated correction ensures that code authored in a case-insensitive environment behaves correctly in Fabric’s case-sensitive model, eliminating the need for manual fixes and reducing migration risk.

(For more information, see the following emulation reference page: Case sensitivity)

---

Code example

Synapse Analytics:

CREATE TABLE Customers (
    CustomerID INT,
    Name NVARCHAR(100)
);
GO

SELECT
    c.customerid,
    C.NAME
FROM
    cusTOMers AS C;

Fabric Warehouse (generated by SQL Tran):

CREATE TABLE Customers (
    CustomerID INT,
    Name VARCHAR(200) /* SQLTRAN FIX: NVARCHAR(100) */
);
GO
SELECT
    c.CustomerID /* SQLTRAN FIX: c.customerid */,
    c.Name /* SQLTRAN FIX: C.NAME */
FROM
    Customers /* SQLTRAN FIX: cusTOMers */ AS c /* SQLTRAN FIX: C */;

---

Training video example

In the example shown, a procedure contains object names with inconsistent casing.

SQL Tran automatically detects these issues and updates the target SQL to restore consistent casing, while adding comments to highlight the adjustments made.

This ensures the code remains functional in Fabric’s case-sensitive environment.

Case sensitivity corrections in translated SQL