SqlServerTroubleMaker (8/19/2012)

---

Bottom right was also showing wrong instance name.

SqlServerTroubleMaker (8/19/2012)

---

New query window
right click --> Connection --> change connection --> Entered dev named instance name -> got it connected to it (looks like it was, but it wasn't),
in fact it was connected somewhere else.

SqlServerTroubleMaker (8/19/2012)

---

Using management studio (10.50.1600 or 10.50.1617.0)

Connecting to named sql server instance (lets call it [DEV-SQL\SqlKing]) version 10.0.4279
--> Cumulative update package 3 (CU3) for SQL Server 2008 Service Pack 2

New query window and properties windows is showing it connected to [DEV-SQL\SqlKing] 10.0.4279
-- > Cumulative update package 3 (CU3) for SQL Server 2008 Service Pack 2

After running following
select serverproperty('servername')
and
select @@servername

Results show as if this query window (I made connect to DEV-SQL\King) is connected to an instance called (PROD-SQL\Pinokio)

Ok, so I figured it is impossible and perhaps it is pulling some incorrect information from somewhere.
So, I went ahead and executed
"Create Database [Test]"

Guess what Test database was created on -- > [PROD-SQL\Pinokio)

While I thought all this time I was connected to "DEV" - [DEV-SQL\King] when in fact it was connected to production "PROD-SQL\Pinokio"
Properties window, query status bar and tab information are all showing wrong instance name.
It is showing as if query is executing against "dev" while in fact it is connected to "production".

I know my management studio is not patched and my SQL server instances need patching too, but
this cannot be out of the box bug (it would be really really dangerous kind of bug to have for product release).

Has anyone experienced or is experiencing this strange management studio behavior?

There is more, but I would like to submit this first and add other interesting discovery after I submit this.

Thanks.