Not a bug per se, but if it keeps blowing memory because of it, then it's a bug.
Try SqlChar and alternate named functions like "Left{100}C" Ugh!!!!! bizarro function names!
Not SubString4K for heaven's sake.
And I want a variant whereby VARCHAR(100) is used. Maybe even the default, which is another breaking change, but is NVARCHAR really the standard? Over double the space for ASCII?
Now "FirstName" is NVARCHAR of course. That is also another reason to have hyper-specific naming.
Not a bug per se, but if it keeps blowing memory because of it, then it's a bug.
Try SqlChar and alternate named functions like "Left{100}C" Ugh!!!!! bizarro function names!
Not SubString4K for heaven's sake.
And I want a variant whereby VARCHAR(100) is used. Maybe even the default, which is another breaking change, but is NVARCHAR really the standard? Over double the space for ASCII? Now "FirstName" is NVARCHAR of course. That is also another reason to have hyper-specific naming.