Tab History, wrong server
After doing multiple server migrations, if you open something in tab history that was for one of the previous servers. Sometimes an implicit connection to the server is still used despite not being connected to that server in Object Explorer. This has caused us to have to troubleshoot something that wasn't working anymore when it fact it is just because the connection was the old server. This forces us to copy the SQL statements to Notepad then open a new window and past so that the connection is set to the connected to server. Some kind of warning of this Historical statement is not pointing to the current server connection would be wonderful.