How can we help you today? How can we help you today?

Tabs don't remember connections when using Azure Managed Instance

Feels like a bug.
It can be replicated using the following steps.

Open SSMS
Connect to Non Azure Managed Instance Server
Create New Query ( 1 )
Connect to Managed Instance Server
Create New Query ( 2 )
Close SSMS
Reopen SSMS

Result
New Query ( 2 ) does not remember what database it was connected to but New Query ( 1 ) does.

Any Solution?
jamesbuckley
0

Comments

20 comments

Sort by
  • Dan_J
    Hi @jamesbuckley

    Thanks for reaching out about this!

    I'm going to be testing this, but before I do so, would you mind confirming what versions of SQL Prompt and SSMS you currently have installed?
    Dan_J
    0
  • jamesbuckley
    Hi @Dan_J,

    It happens on all variations as far as I'm aware.

    My SSMS:

    SQL Server Management Studio 19.0.20209.0+f9a9d8f6
    SQL Server Management Objects (SMO) 16.200.48036.0+7d3b143d945e1aa638acdb02c0364e263d5ec973
    Microsoft T-SQL Parser 16.0.22524.0+62eedb15cd3cde34e51c8fbbdf9b06e575ec912e
    Microsoft Analysis Services Client Tools 16.0.19993.0
    Microsoft Data Access Components (MDAC) 10.0.19041.3208
    Microsoft MSXML 3.0 6.0 
    Microsoft .NET Framework 4.0.30319.42000
    Operating System 10.0.19045

    And SQL Prompt is 10.13.14.2694.

    Cheers,
    James
    jamesbuckley
    0
  • Dan_J
    Hi @jamesbuckley

    Thanks for your reply on this.

    I think I have a reproduction of this issue here and have engaged our development team for their input.

    I will come back to you on this as soon as I have an update for you.
    Dan_J
    0
  • Dan_J
    Hi @jamesbuckley

    Following my last message, I'm pleased to advise that a fix for this issue is due to be included in the next release of SQL Prompt. 

    I'm not sure yet if that will be next week, or in a few weeks time, but I will let you know as soon as I know more.

    Thanks for your patience with us on this.
    Dan_J
    0
  • jamesbuckley
    thanks @Dan_J that's great news
    jamesbuckley
    0
  • jamesbuckley
    Hi @Dan_J

    Saw the changelog for 10.13.16.3650 included the following...

    Fixes

    • Fixed an issue where tabs would not restore when connection was of Active Directory Password type.

    Was this the bug fix for the above?

    If so, it's not just the Active Directory Password authentication that is an issue, we are using
    Azure Active Directory - Integrated
    and still having the issue

    Cheers,
    jamesbuckley
    0
  • Dan_J
    Hi @jamesbuckley

    I'm sorry this hasn't fixed the issue for you! 

    I've gone back to our development team on this and will come back to you as soon as I have an update.
    Dan_J
    0
  • Dan_J
    Hi @jamesbuckley

    Just to update you that I'm continuing to keep an eye on our development team's progress on this and will come back to you as soon as I have more for you.

    Thanks for your on-going patience with us on this!
    Dan_J
    0
  • jamesbuckley
    Hi @Dan_J

    No problem, its a nuisance more than a problem, so I understand if it's not prioritised.

    Cheers,
    jamesbuckley
    0
  • Dan_J
    Hi @jamesbuckley

    Appreciate your continued patience with us on this. I hoping to have an update for you soon.
    Dan_J
    0
  • Dan_J
    Hi @jamesbuckley

    Thanks for your on-going patience with us on this. I appreciate I said this in my last update also, but I'm hoping to have an update for you on this shortly.

    In the mean time, our development team have asked if you could confirm if this issue also occurs for you when connecting via Azure AD Integrated?
    Dan_J
    0
  • jamesbuckley
    Morning @Dan_J,

    Yes, we're using Azure AD Integrated, it's on the comment above from October 30, 2023 9:53AM.
    jamesbuckley
    0
  • Dan_J
    Hi @jamesbuckley

    Thanks for your on-going patience with us on this. 

    I'm continuing to keep a close eye on progress made on this by our development team and will come back to you as soon as I have more for you.
    Dan_J
    0
  • jamesbuckley
    Hi @Dan_J

    It is a bit of an annoyance that it was meant to be resolved with a fix in October which didn't work, and is now not being looked at 5 months later but it is what it is.

    Cheers,

    James
    jamesbuckley
    0
  • jamesbuckley
    Hi @Dan_J

    Any update on the priority on this?

    Thanks,

    James
    jamesbuckley
    0
  • Dan_J
    Hi @jamesbuckley

    I'm very sorry we're still waiting for a resolution on this.

    This is still with our development team currently. I'm chasing this regularly, and have just done so again. I'm continuing to keep a very close eye on progress. 

    I appreciate this is taking a while, thank you for your patience. 

    I'll come back to you on this again as soon as possible.


    Dan_J
    0
  • Dan_J
    Hi there @jamesbuckley

    My sincere apology again for the on-going wait on this, I appreciate you have been waiting for a fix for this for some time now.

    Our team are looking at this, however there have been some delays along the way. 

    I am continuing to keep a close eye on progress on this and hope to have a better update for you very soon.
    Dan_J
    0
  • jamesbuckley
    Thanks @Dan_J

    I appreciate you keeping me updated. This is still an issue and is still annoyance on a day to day basis so the help would be appreciated.
    jamesbuckley
    0
  • jamesbuckley
    Hi @Dan_J, any update?
    jamesbuckley
    0
  • jamesbuckley
    Hi @DanC, I know this isn't an issue you've commented on previously, but just found your name on another channel and @Dan_J hasn't been active since the end of December, so assuming he's left the company. Is there any chance you could look at helping with this issue? It seems a smallish bug, which has been about since October 2023, but it is a daily annoyance. Cheers, James
    jamesbuckley
    0

Add comment

Please sign in to leave a comment.