May 5, 2020 at 11:26 pm
Does anyone knows that SQL 2019 came up with tables to contain additional character lengths vs SQL 2017?
May 6, 2020 at 9:07 am
Additional to what? Both versions support varchar(max) and nvarchar(max), in which you can insert a 2GB string. If you need more than that, consider Filestream, which has been part of the product since 2012.
John
May 6, 2020 at 11:12 am
I'm not aware of a change like you're describing. Microsoft always publishes a "what's new" article on each version. Look through there. Do you mean the new verbose warnings on truncation errors (I think the oldest & most voted ticket in their backlog)?
Maybe clarify what it is you're looking for.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 6, 2020 at 1:13 pm
only changes to "character size" was done on 2012 with the inclusion of new _SC collations to allow for UTF-16 and the expansion done by 2019 to allow for char and varchar.
and again you need to learn to RTFM - having someone to do the dirty work for you is not professional.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply