Azure data studio editor tabs

  • Hi--Does anyone one know what the "M" and "1, M" indicate in the editor tabs (see screenshot)? I'm stumped

     

    Screen Shot 2021-09-22 at 6.32.33 PM

    • This topic was modified 3 years, 2 months ago by  jmetape. Reason: typo
  • The number I have. It's the number of statements that have perceived problems.

    2021-09-23_7-12-42

    Those three tabs have exactly that number of SQL statements in each that looked wrong because they were unconnected from a database.

    The M... I'm working on. I haven't replicated it yet.

    "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

  • I think I've got it. The M, not sure why M, appeared when I had an uncommitted change in source control. I staged it and then committed it, and the M went away.

    Why M? I've got nothing. I'm going to ask #sqlhelp and see if Vicki (Microsoft Dev Lead) answers me.

    "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

  • I did a little more research and testing and I've got it. "M" in this case means that you've got a script that's in source control. You've made changes to it and saved them. This means the script is "Modified". I know this now because if you hover over the file name in the Explorer window, a tool tip pops up and shows full text. I also have a "U" for "Untracked", which I think means I haven't staged it yet.

    "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

  • Ah, and another clarification. I was wrong about the numbers being statements. It's count of lines of code that the tool thinks may have problems. That's why one tab has a number and another tab does not.

    Sorry about the bad info earlier.

    "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

  • That's awesome info. Thank you so much for taking the time to look into that!

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

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