Oracle客户端和服务器分离的优点
在编写与 MS SQL 数据库配合使用的应用程序时，我们所做的只是指定连接参数（硬编码或动态）。当我们在机器上安装该应用程序时，我们并不关心该机器是否有适当的工具来建立与 MS SQL Server 数据库的连接。
然而，在 Oracle 中情况有所不同。我们必须确保要安装该应用程序的所有计算机都已设置 Oracle 客户端。否则它将无法工作。现在我的第一个问题是这提供了什么优势？第二个问题是是否有某种方法可以在 SQL Server 中实现类似的效果？
When writing an application that'll work with MS SQL database all we do is just we specify the connection parameters (either hard coded or dynamically). And when we install that application on a machine, we don't care if that machine has the proper tool to make the connection to the MS SQL Server database available.
However, in Oracle things are different. We have to make sure that all the machines that we want to install the app has Oracle Client set up. It will not work otherwise. Now my first question is what advantage does this provide? And the second one is if there's some way to achieve the similar in SQL Server?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
实际上，如果 Oracle 拥有 Windows，则 Oracle 客户端将与 Windows 一起安装，而 SQL Server 客户端将单独安装。这不是优点和缺点的问题，而是谁拥有堆栈并可以将其软件与操作系统捆绑在一起的问题。
根据您构建 Oracle 应用程序的具体方式，您很有可能使用 Oracle Instant Client 或 Oracle 瘦（类型 4）JDBC 驱动程序，用于提供与数据库的连接。其中任何一个都可以由您的应用程序安装，无需单独安装 Oracle 客户端。
Realistically, if Oracle owned Windows, the Oracle client would be installed with Windows and the SQL Server client would be a separate install. It's not a matter of advantages and disadvantages, it's a matter of who owns the stack and can bundle their software with the operating system.
Depending on exactly how you are building your Oracle application, there is a good chance that you can use the Oracle Instant Client or the Oracle thin (type 4) JDBC driver to provide connectivity to the database. Either of these can be installed by your application without requiring a separate Oracle client install.