Christoph Mettler on 30 May 2023 11:45:19
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
Bogdan Crivat (administrator)
We're working on this. We'll share details as soon as we have a clear timeline.
- Comments (5)
RE: extent storage capacity of varchar(8000) to varchar(max)
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. )
RE: extent storage capacity of varchar(8000) to varchar(max)
How is this going? Its almost one year old..
RE: extent storage capacity of varchar(8000) to varchar(max)
Any updates on this? This is blocking the import of data from postgresql where json is stored in a column.
RE: extent storage capacity of varchar(8000) to varchar(max)
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.
RE: extent storage capacity of varchar(8000) to varchar(max)
We're working on this. We'll share details as soon as we have a clear timeline.