Karl Burtram

@markroosenlom are you getting an error message when the connection fails? either as an error message dialog or in the "Help->Developer Tools" Console? Thanks!

@jheavin-iit do you see any errors in the "Help>Developer Tools" Console while the subscriptions are loading? @cssuh or @alanrenmsft any suggestions on how to troubleshoot what's going on here?

@anthonydresser it looks like the default value for textSize is `2147483647` so that doesn't seem to match-up with the bug report. I'd need to investigate to understand this behavior.

The current implementation is that query execution options are applied to the session each time a query is executed. If the above script is executed as a single unit then...

@EklipZgit thanks for providing the additional context. I also was unable to repro the above problem using the following repro. It's likely there is some detail I'm missing. 0. Open...

@smartguest should we close out this older PR since I think it will still need a bit of work to get merged? We can reopen later if we pick this...

@smartguest should we close out this older PR since I think it will still need a bit of work to get merged? We can reopen later if we pick this...

Closing older PR without recent activity. Please reopen if working on this area again.

As far as I understand this is not associated with plan source code changes in the May release branch. I thought this was to track reenabling the "Fail on console.error"...

I added some notes into https://github.com/microsoft/azuredatastudio/issues/7643 regarding the current behavior. Where basically the query options are set each time a query is executed. IIRC, SSMS splits the options into two...