SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Strange Management Studio 2008 R2 (10.50.1600 and 10.50.1617) behaviour


Strange Management Studio 2008 R2 (10.50.1600 and 10.50.1617) behaviour

Author
Message
SqlServerTroubleMaker
SqlServerTroubleMaker
SSC Rookie
SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)

Group: General Forum Members
Points: 30 Visits: 140
**********************************
Would be nice to know if this was already addressed or if MSFT was planning to address it any time soon?

--Looks like this issue was reported in 2009
https://connect.microsoft.com/SQLServer/feedback/details/434465/management-studio-can-display-connection-to-wrong-server

--More about the issue with pretty print screens
http://staxmanade.blogspot.com/2009/04/potentially-serious-bug-sql-server-2008.html
***********************************************************************

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.
demonfox
demonfox
SSCommitted
SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)

Group: General Forum Members
Points: 1525 Visits: 1192
you had it opened brand new
or the specific query window was opened as connected to prod ?
when you open a query window , specific to an instance; it sticks to the instance only..

~ demonfox
___________________________________________________________________
Wondering what I would do next , when I am done with this one Ermm
demonfox
demonfox
SSCommitted
SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)

Group: General Forum Members
Points: 1525 Visits: 1192
Also, what's the connection info in the bottom right of the query window ??

[Note : for a new query, two options are available , one is with current conn. and other is database Query.]

~ demonfox
___________________________________________________________________
Wondering what I would do next , when I am done with this one Ermm
SqlServerTroubleMaker
SqlServerTroubleMaker
SSC Rookie
SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)

Group: General Forum Members
Points: 30 Visits: 140
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
SqlServerTroubleMaker
SSC Rookie
SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)

Group: General Forum Members
Points: 30 Visits: 140
Bottom right was also showing wrong instance name.
SqlServerTroubleMaker
SqlServerTroubleMaker
SSC Rookie
SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)

Group: General Forum Members
Points: 30 Visits: 140
This wouldn't apply because query windows gets connection changed ->
Right click-> Connection--> change connection.

"[Note : for a new query, two options are available , one is with current conn. and other is database Query.]"
demonfox
demonfox
SSCommitted
SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)

Group: General Forum Members
Points: 1525 Visits: 1192
SqlServerTroubleMaker (8/19/2012)
Bottom right was also showing wrong instance name.

That's strange ....
I never encountered such issue ...
you said that there is something else too , what was that ??

~ demonfox
___________________________________________________________________
Wondering what I would do next , when I am done with this one Ermm
demonfox
demonfox
SSCommitted
SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)

Group: General Forum Members
Points: 1525 Visits: 1192
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.


really !! I tried the same thing , but it does change connection ..and yes, works, as it should..

~ demonfox
___________________________________________________________________
Wondering what I would do next , when I am done with this one Ermm
Jared Karney
Jared Karney
SSCarpal Tunnel
SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)

Group: General Forum Members
Points: 4986 Visits: 3694
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.
Sounds to me like someone migrated an instance incorrectly. For example, when we move from an existing machine to a new one we rename the server. Someone did not do this in your case. Was this server once a production server? Was the master database moved from another production server to this one?

Thanks,
Jared
PFE - Microsoft
SQL Know-It-All
How to post data/code on a forum to get the best help - Jeff Moden
SqlServerTroubleMaker
SqlServerTroubleMaker
SSC Rookie
SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)

Group: General Forum Members
Points: 30 Visits: 140
Thanks for all suggestions and for trying to help.
New instance it wasn't migration. System DBs were not migrated.
Instances are new (user databases were migrated/restored from another environment).
Note: issue is not persistent. It happens randomly. Also it also hits different instances.
Lets say I am connecting to InstanceA, while it will always show as if connected to InstanceA,
the actual instance would be InstanceB and at some time "C", "D" or other. It is random and very strange.

"Sounds to me like someone migrated an instance incorrectly. For example, when we move from an existing machine to a new one we rename the server. Someone did not do this in your case. Was this server once a production server? Was the master database moved from another production server to this one?

Thanks,

Jared
SQL Know-It-All
"
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search