How to install the SQL 2000 and SQL2005 method on the same machine

1, because the SQL2000 installation process can not modify the instance name, so the installation process must first install SQL2000, and then install sql2005. You must modify the SQL instance name when you install sql2005, otherwise it will conflict with the instance name of sql2000.

2, after the installation of sql2005, began to use SQL2000 client tools to connect sql2005, the results report can not be connected with the SQL2000 client tools, can only use the SQL2005 Client tool connection, It is proven that the SQL2005 client tool can connect both sql2000 and sql2005.

3, the server installed after the completion of the remote connection to the SQL Server to try, the results are always connected sql2005, can only connect to the sql2000. The original SQL2000 server with the port is always 1433 ports, and sql2005 use dynamic port, if the program to connect sql20005 server, the program how to know sql2005 server with what port? Originally sql2005 provides a SQL Brower service that enables you to query the SQL Brower service to 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, locate the protocol below the instance name of SQL, double-click the TCP/IP protocol on the right, and enter the SQL run port on the Second tab in Ipall (Note that you cannot fill both dynamic and static ports, otherwise SQL will not start the next time). Restarting the SQL service after the modification is complete takes effect.

4, modify the port after the connection found still can not connect, the original also need to open sql2005 remote landing services.

The default in Microsoft SQL Server 2005 is that remote logins are not allowed, and an error "Provider:sql network interface, error:26-locating the specified server/instance" appears, the following method opens:

The Configuration tool->sql the server perimeter configuration-> service and the perimeter configuration of the connection-> open the Database engine node under the MSSQLSERVER node, select Remote Connection, and then recommend that you use tcp/ IP and Named pipes ", after determining, restart the Database tutorial service will be available.

5, remote Landing services and ports are modified after the connection should be no problem? Results remote connection sql2000 found no problem, but the connection sql20005 still not, in the SQL2005 Client Connection tool to enter the SQL service you want to connect, sql2000 directly into the server's IP address can be, How can I enter a service that allows the client tool to connect to the sql2005? 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 client connections was later modified, and the result was still not. No way, only to online Google a turn, and finally in an English article found the way to connect. Originally in accordance with the format of the normal entry is wrong, you need to change to: IP address + comma + port number to do. A try, sure enough. Then try to see if you can connect through the. NET program access, and the results are OK.

Summary: It is because the connection entered the wrong format, I got a day to find a way, really depressed, I do not know why sql2005 do not use the usual method, but to change the colon to a comma connection.