extend storage capacity of varchar(8000) to varchar(max) for warehouse

[c_mettler]

The maximum string length of 8000 is often considered too short to store longer descriptive data or embed a JSON value within a text field in a database. Dividing the data into smaller chunks and store them across multiple text fields or in separate tables is unnecessarily cumbersome.

data types ref: CREATE TABLE - SQL Server | Microsoft Learn

[bogdanc]

We're working on this. We'll share details as soon as we have a clear timeline.

[fbcideas_migusr]

Hope this gets resolved soon. I've noticed issues with shortcuts in lakehouses and field types that go beyond varchar(8000) are causing errors on the SQL endpoint.

[fbcideas_migusr]

Any updates on this? This is blocking the import of data from postgresql where json is stored in a column.

[fbcideas_migusr]

How is this going? Its almost one year old..

[todd_chittenden]

I really wish Microsoft would work on BASIC and CORE functionality like this instead of the shiny "Ooooo and Ahhhhh" advanced stuff. I would take this over CoPilot integration 6 days a week and twice on Sundays! (This and IDENTITY columns, and PRIMARY KEY enforcement, etc. )

[tomas2]

Mirroring from CosmosDB got us into problem as some parts of document can easy go over 8000 and we cannot reuse the data!

[bogdanc]

This feature is in public preview in warehouse: Announcing public preview of VARCHAR(MAX) and VARBINARY(MAX) types in Fabric Data Warehouse | Micros...

[ernie8925]

Will this feature also be added to Lakehouses? It seems that I can create fields with >8000 size in Lakehouses and store large content in it. But if I query the data through the SQL analytics endpoint, then these fields are truncated to 8000.

[Trentor]

I'm also having issues with the Lakehouse endpoint being truncated to 8000 characters, and this is causing me issues trying to parse some JSON. Any idea when how long for a resolution? I'm just trying to work out if I should find a work around.