FIX: The connection information is incorrect after you use "Change Connection" to connect to another server before the initial connection is completed in SQL Server Management Studio in SQL Server 2008

Article translations Article translations
Article ID: 975414 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario:
  • In Microsoft SQL Server 2008, you use SQL Server Management Studio (SSMS) to connect to a database server. For example, the name of the database server that you connect to is "Server1."
  • You perform the following operations:
    • Open a new query window in SSMS.
    • Before the connection is completed, you right-click the new query window, point to Connection, and then click Change Connection… to connect to another database server. For example, the name of the other database server that you connect to is "Server2."
In this scenario,the connection information states that you are connected to "Server2." However, you are still working in the context of "Server1."

For example, the task bar at the lower-right of the window shows the server name of "Server2."Additionally, IntelliSense is available for objects on "Server2." However, the database server name "Server1" returns when you run the following statement:
SELECT @@SERVERNAME
If you try to use objects on "Server2," you will receive an error message that states the object is invalid. However, you can use objects on "Server1" successfully.

RESOLUTION

The release version of SQL Server 2008

The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
973601 Cumulative update package 7 for SQL Server 2008
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released

SQL Server 2008 Service Pack 1

Important You must install this fix if you are running SQL Server 2008 Service Pack 1.

The fix for this issue was first released in Cumulative Update 5 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
975977 Cumulative update package 5 for SQL Server 2008 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

WORKAROUND

To work around this issue, change the connection for a new query window when the initial connection is completed. You can run the following statement to make sure whether you are running in the context of the new connection:
SELECT @@SERVERNAME

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

REFERENCES

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems


For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 975414 - Last Review: September 21, 2009 - Revision: 1.1
APPLIES TO
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Workgroup
Keywords: 
kbsurveynew kbfix kbqfe kbexpertiseadvanced KB975414

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com