Oracle Remote Connectivity

Oracle remote connection is not directly using the IP plus port form, but using TNS (Personal feeling and ODBC DSN a bit similar, somewhere to save some settings, and then give these settings a name, when used to directly write the name on the line)

TNS Directory Location:

installation directory \network\admin\tnsnames.ora

ORCL32 =      = = (PROTOCOL = TCP) (HOST = localhost) (PORT = 1521))    =      = dedicated)       = orcl)   ))

The client uses ORCL32 on the connection usage.

There are several ways to connect the Oracle database in Windows

1. Using ODBC

32-bit window with Microsoft ODBC for Oracle driver (but also to install the Oracle client, if you install both 32-bit and 64-bit, you must write the 32-bit path in the PATH environment variable before 64 bits)

64-bit window with no self drive

2.. NET Framework Data Provider for Oracle

VS2010 started Microsoft has advised against using this to connect to the Oracle database.

3.. NET Framework Data Provider for OLE DB

VS2013 started Microsoft has advised against using this to connect to the Oracle database.

4. Install the Oracle client (if the server side of the native installation does not need to install the client again)

32-bit, provides vs development tools

64-bit, no vs development tool available (because vs has so far not had 64-bit)

Note When developing Oracle database-related programs in VS:

1.VS so far there is no 64-bit version, so when connecting to Oracle in Server Explorer in VS, you can only use 32-bit Oracle connections (if you have 64-bit Oracle clients installed, unfortunately, you must also install 32-bit clients)

If you want to use Microsoft's own ODBC connection, you must write the 32-bit path in the PATH environment variable before the 64-bit

2. The developed program 32-bit 64-bit, whether the corresponding version of the Oracle client must be used is unknown.

I'm telling you what I've heard, Microsoft says, and there are countless developers suggesting that Microsoft develop 64bit Visual Studio, but Microsoft didn't do it because Microsoft surveyed the vast majority of deep-seated needs, and they were looking for 64bit of Visual Studio, Because they think 64bit programs may have higher performance. But this is not really the case, the 64bit program on the X86-64 processor does not bring significant performance improvement, it just increases the processor's addressing range, can use the larger memory. For VS, this is not a memory-sensitive program, and it's not very necessary to migrate to 64bit. In addition, there is a historical reason, that is, Microsoft has not finished 64bit JIT debugger's edit and continue function, because the 64bit JIT is the C + + team to do, and the native CLR team 32bit JIT is a lot different, Microsoft is now trying to unify both. If Microsoft launches 64bit VS, the debugging experience will be limited, which is why Microsoft has not launched 64bit vs for a long time.

Oracle Remote Connectivity