Install SQL2000 and SQL2005 conflict resolution on the same server

Install SQL2000 and SQL2005 on the same server and record the problems encountered during installation to facilitate friends who have the same problems. 1, because the instance name cannot be modified during the SQL2000 installation, the SQL2000 must be installed during installation and then the SQL2005 will be installed. The SQL instance name must be modified when the SQL2005 is installed, otherwise the instance name of the SQL2000 conflicts. 2, after installing SQL2005, begin to prepare to connect SQL2005 with SQL2000 Client tool, result report cannot connect with SQL2000 Client tool, can connect with SQL2005 Client tool only, It is proven that the SQL2005 client tool can connect both SQL2000 and SQL2005. 3, after the installation of the server, ready to use the remote connection SQL Server to try, the result is always connected to SQL2005, can only connect to the SQL2000. The port used SQL2000 server is always 1433 ports, The SQL2005 uses a dynamic port. If the program is connected to the SQL20005 server, how does the program know what port the SQL2005 server is using? Originally, SQL2005 provided a SQL Brower service that enabled you to query SQL The Brower service will know which Port SQL2005 is using now. Because the project needs, this SQL2005 dynamic port needs to be changed to static, the modification process is as follows: Run SQL Configuration Manager, find the protocol under the instance name of SQL, double-click the TCP/IP protocol on the right, In the Second tab, enter the SQL run port on the Ipall (note that the dynamic and static ports cannot be filled in at the same time, otherwise the SQL will not start the next time), and the SQL Service can take effect when the modification is complete. 4, modify the port after the connection found still can not connect, the original also need to open SQL2005 remote landing services. In Microsoft SQL Server 2005, by default, remote logins are not allowed, and an error "Provider:sql network interface, error:26-locating the specified server/instance" appears, the following method can be opened: Configuration Tool->sql SE RVer the Perimeter Application Configurator-> service and the perimeter configuration of the connection-> open the database Engine node under the MSSQLSERVER node, choose Remote Connection, then recommend "Use TCP/IP and named pipes simultaneously" to determine , restarting the database service is OK. 5, remote Login services and ports are modified after the connection should be no problem, the result of remote connection SQL2000 found no problem, butIs the connection SQL20005 still not, in the SQL2005 of the Client Connection tool needs to enter the SQL service you want to connect, SQL2000 directly into the server's IP address, then how to enter the client tool to connect to the SQL2005 service? Since SQL2005 modified the port, it should be entered according to the normal input format: IP address + colon + port number should be OK. The results were tried and found still not. The default port for the client's connection is modified and the result is still not. There's no way. Only to online Google a turn, the results finally in an English article found the connection method, the original according to the normal format input is wrong, need to change to: IP address + comma + port number to do