August 19, 2012 at 7:10 pm
**********************************
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
--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.
August 19, 2012 at 7:30 pm
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:
August 19, 2012 at 7:35 pm
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:
August 19, 2012 at 7:36 pm
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.
August 19, 2012 at 7:37 pm
Bottom right was also showing wrong instance name.
August 19, 2012 at 7:39 pm
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.]"
August 20, 2012 at 8:41 am
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:
August 20, 2012 at 8:48 am
SqlServerTroubleMaker (8/19/2012)
New query windowright 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:
August 20, 2012 at 9:09 am
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?
Jared
CE - Microsoft
August 20, 2012 at 10:47 pm
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
"
August 20, 2012 at 10:47 pm
It doesn't happen all the time. It happens at random.
August 20, 2012 at 10:55 pm
Something else part goes like this.
I am connecting to InstanceA which is SQL Server + SP2.
I have other instances in my environment that are RTM.
When it all works correctly it shows under bottom status bar that I am
connected to InstanceA (10.0 SP2). When it is connected to wrong location (lets call it InstanceBAD)
it is showing under bottom status bar IntanceA (10.0 RTM).
How about that?
I don't know what is it, but it is really annoying especially when I cannot put my finger on what it is.
I will probably just end up applying latest SP, which I am sure is what MSFT support will ask me to do anyway 🙂
I was simply very curious to know what in the world is causing it.
Management studio BUG due to the lack of SP or some networking or windows configuration issue?
Thanks
August 21, 2012 at 9:32 pm
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
--More about the issue with pretty print screens
http://staxmanade.blogspot.com/2009/04/potentially-serious-bug-sql-server-2008.html
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply