Results different in Azure Data Studio vs SSMS

  •  

    Any idea why this would be the case? I see the result in Azure Data Studio but some of the strings are truncated in SSMS.

    Also, if you notice, IIADR3 has a length of 1, but it’s not space or null. So, not sure what it is. Wondering if you guys came across this situation before.

    I've attached the screenshot for this issue. Any help would be appreciated.

     

    Attachments:
    You must be logged in to view attached files.
  • Most people won't download a word or excel document from a forum - too risky.  But - without seeing what you have my guess is the default display settings in SSMS are the issue.  SSMS uses a default size for the number of characters displayed in either grid or text mode and truncates the display if the column exceeds that length.

    Now - a column that has an apparent 'blank' but isn't a space is going to be some type of control character.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • Thank you for your response. That makes sense. But why would Azure Data Studio shows the perfect results but SSMS don't?

  • SQL_Surfer wrote:

    Thank you for your response. That makes sense. But why would Azure Data Studio shows the perfect results but SSMS don't?

    As I stated before - SSMS has a defined limit on column size that will be *displayed*, where ADS does not have that limit.  Instead, I think ADS just limits the size of the grid column but still displays the full data.

     

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • SQL_Surfer wrote:

    Thank you for your response. That makes sense. But why would Azure Data Studio shows the perfect results but SSMS don't?

    Because it has different defaults for returned column size just like the same model of two cars may have different wheel styles.

    --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)

  • SQL_Surfer wrote:

    Thank you for your response. That makes sense. But why would Azure Data Studio shows the perfect results but SSMS don't?

    The default max column size in SSMS is 256 if I remember correctly. It's one of the first things I change when I install it. You can change it in options to a max of 8192.

Viewing 6 posts - 1 through 5 (of 5 total)

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