May 25, 2016 at 8:04 pm
Comments posted to this topic are about the item Large strings
May 25, 2016 at 11:43 pm
This was removed by the editor as SPAM
May 26, 2016 at 5:42 am
Easy enough to help get the brain moving. Thanks.
May 26, 2016 at 9:51 am
Well, the documentation for nchar and nvarchar still says that the the value can be any number from 1 to 4000 or max, and 5000 is clearly not in that range, so I was actually expecting an error, but that wasn't one of the choices.
Drew
J. Drew Allen
Business Intelligence Analyst
Philadelphia, PA
May 26, 2016 at 10:54 am
drew.allen (5/26/2016)
Well, the documentation for nchar and nvarchar still says that the the value can be any number from 1 to 4000 or max, and 5000 is clearly not in that range, so I was actually expecting an error, but that wasn't one of the choices.Drew
How would that apply? Both variables are VARCHAR (or were when I looked at the question).
Cheers!
May 26, 2016 at 11:54 am
drew.allen (5/26/2016)
Well, the documentation for nchar and nvarchar still says that the the value can be any number from 1 to 4000 or max, and 5000 is clearly not in that range, so I was actually expecting an error, but that wasn't one of the choices.Drew
Wrong data types. Here's the correct link: https://msdn.microsoft.com/en-us/library/ms176089.aspx
May 26, 2016 at 12:03 pm
Got the answer but misread the question - did not notice the [font="Courier New"]varchar(MAX)[/font] vs [font="Courier New"]varchar(5000)[/font] !
Lesson repeated: when looking at T-SQL do not overlook details.
May 26, 2016 at 12:07 pm
Jacob Wilkins (5/26/2016)
drew.allen (5/26/2016)
Well, the documentation for nchar and nvarchar still says that the the value can be any number from 1 to 4000 or max, and 5000 is clearly not in that range, so I was actually expecting an error, but that wasn't one of the choices.Drew
How would that apply? Both variables are VARCHAR (or were when I looked at the question).
Cheers!
:blush: I guess my morning caffeine hadn't totally kicked in, yet. It's a good thing that producing an error wasn't one of the choices.
Drew
J. Drew Allen
Business Intelligence Analyst
Philadelphia, PA
May 26, 2016 at 12:35 pm
I guess my morning caffeine hadn't totally kicked in...
Heh, been there more times than I'd care to admit 🙂
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply