Skip to content

JSON Columns fits only 2033 Bytes flows over into next row - TSQL FOR JSON PATH option #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
veercv opened this issue Jul 13, 2020 · 1 comment
Closed

JSON Columns fits only 2033 Bytes flows over into next row - TSQL FOR JSON PATH option #3

veercv opened this issue Jul 13, 2020 · 1 comment

Comments

@veercv
Copy link

veercv commented Jul 13, 2020

Using the TSQL option to return native JSON response from Azure SQL - select * from [table FOR JSON path exceeding 2033 Bytes on a column receive only first Column invalid JSON response.
@veercv
Copy link
Author

veercv commented Jul 13, 2020

Adding cursor.fetchall() provides iteration to multiple rows for resultset columns exceeding 2033 Bytes.

@veercv veercv closed this as completed Jul 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@veercv