Microsofterinstellato - ok, lots to respond to here...sorry its long....we all have work-to-do.
1.
"First, my recommendation if you find a bug in SSMS is to always, please, check to see if an issue already exists on the feedback/ideas site." - NOTE: it's not obvious how to get to the right place (link would be nice). I did find the known issues on the SSMS download page.
I binged "ssms feedback/ideas site" and this is https://learn.microsoft.com/en-us/sql/sql-server/sql-server-get-help?view=sql-server-ver16 .... That page is SQLServer centric not SSMS centric and it's not obvious how to get to SSMS know issues.
Also, I don't know how to up-vote a bug?? Where do you do that....link please.
So two issues: The first one is similar to this:
| Azure SQL Managed Instance | Viewing database properties for a SQL MI database may return the error "Subquery returned more than one value. This isn't permitted when the subquery follows =, !=, <, <=, >, >= or when the subquery is used as an expression. (.NET SqlClient Data Provider)". | There's a known problem due to incorrect data in msdb. To resolve, remove back up history. For example, EXECmsdb..sp_delete_backuphistory @oldest_date = '<current date>'. |
I have also seen this bug with Azure VM SQL Servers. The source of that problem is the VM snapshots have non-copy-only agent backups that invade the backup history. These entries have the physical_database_name as the database "name". So the query to find the last backup-date fails because a select subquery returns multiple rows that expects just one database name for the same dbid (part of this issue is that db_id (rightly) resolves both the physical_database_name and name to the same thing).
The other issue I have is:
when I click on Replication->LocalSubscription (rightclick)->NewSubscription... -> Publisher(FindSQLServerPublisher) -> (ConnectToServer Dialog) -> <I specify a Managed-Instance and authenticate>
* v18 fine.
* v19.1, SSMS disappears and restarts....ugh.
My Plugin comment: In particular I was thinking of POORSQL. Looks like it's been a few years since the last build. I admit I don't know motivations. and another post mentioned "Abandonment" as a reason for some old plugins. This was unknowledgeable frustration on my part. I have no stats to back it up. But you think so many versions might dissuade people?
Lying/Misleading - I am sorry if that's what was communicated. Not my intent. But being a DBA for 20+ years and more than that in IT, I have seen big software companies "change direction" on key products including MS. Its apparent MS wants their SQL business to go to Azure from Client-site. right? Business pressure is that direction. I don't think it's a stretch to think a tool called Azure-Data-Studio will complete with SQLServer-Management-Studio in the minds of those that make MS strategic direction.... especially a weird release pattern: 18.12 - 19.1 - 20... makes one think?
But you are official MS so will take what you say as the truth. Sorry what I said impugned your integrity. that would not be right. Thanks for your time.
