This content has been marked as final. Show 2 replies
EZCONNECT eliminates the need for service name lookups in tnsnames.ora files when connecting to an Oracle database across a TCP/IP network
also as examples :
My quick thoughts are that while EZConnect isn't dependent on any environment variables/files to look up for connection information, it also doesn't cover all the additional parameters that are available in a tnsnames file. The tnsnames also has the advantage of acting like a centralised connection string - change once and all apps/services that use it will read the new connection details, rather than needing to update each app's EZConnect connection string individually.Agreed. Within the documentation you can also read :
Easy Connect naming is not suitable for large or complex environments with advanced features, such as connection pooling, external procedure calls, or Heterogeneous Services, that require additional connect information. In these cases, another naming method is recommended.
We normally use the Easy Connect naming method for "simple" connections, but we discourage it within applications, where tnsnames guarantees a better control.