the workaround for procs truncating varchar and nvarchar max output fields

  • Hi , assuming the answer at https://stackoverflow.com/questions/50474892/return-strings-from-sql-server-stored-procedures-being-truncated is correct and my peer's version of sql is Microsoft SQL Server 2016 (SP3) (KB5003279) - 13.0.6300.2 (X64) Aug 7 2021 01:20:37 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor) , and assuming he can set provider and version in his conn string, what should he set provider  and version  to in the native client?

  • The real trouble is most likely the way that someone is concatenating the string.  Post the code doing the concatenation and we can probably confirm the issue and, if so, the easy fix for it all.

     

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • thx jeff.  that's (code or data generated) too proprietary to post here.  and/or too expensive to obfuscate.

    what did you think you would see?  I already asked my peers if there was too much whitespace etc.   the purchase orders they are building have tons of data in them.  and their work around if we cant get an answer here will be to return a resultset instead of one single payload of what i believe is json formatted data.

    • This reply was modified 1 week, 4 days ago by  stan.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply