Chapter 4 using linked server of MS SQL7

The first two articles talk about how to connect to ORACLE. I have also tried the ODBC method.
Method:
1. First, create a system DSN. Only the system DSN can be used.
2. Use the first two methods to add the LINKED SERVER
3. Then we can use it normally, but I tried to find that this method is not stable.
Note the following:
In step 2, Provider should be MSDASQL
Provider name should be
Select Microsoft ole db Provider for ODBC"
The test is successful on UNIX ORACLE7 and NT4 SP5 SQL7.
I have also set up connections between SQL7 and SYSBASE, but it is strange that SQL7 customers can direct to the SYSBASE server.
Method:
1. Install the SYSBASE client on the local server and set it to be connected to the server
2. Open the SQL7 client network utility and add the server. The address is direct.
The IP address pointing to the SYSBASE server. The port number is the same as that of the SYSBASE client.
3. The method for adding a linked server is the same as that for adding a mssql server.
The test is successful on unix sysbase and NT4 SP5 SQL7.
The test is successful on unix sysbase and WIN98 SQL7.
The easiest way to access SQL6.5 in SQL7 is to set the connection of the 6.5 server in the client network utility.
However, this connection can only be used in query analyzer, but cannot be managed in enterprise manager.
Let's talk about the remote server and linked server. If we talk about it, someone will say that this is "what is the canvas? It stinks and grows ".