多数主要数据库供应商都提供某种形式的联合技术，该技术支持将来自其他数据库的表整合到供应商环境中。
Most major database vendors offer some form of federation technology which allows you to incorporate tables from other databases in your vendor's environment.
这大大简化了Web应用程序（通过封装差别，在一个通用的API 下支持不同的数据库供应商）的创建。
This greatly simplifies creating Web applications designed to support different database vendors by encapsulating the differences under a common API.
SpringDAO：JDBC DAO抽象层提供了有意义的异常层次结构，可用该结构来管理异常处理和不同数据库供应商抛出的错误消息。
Spring DAO: the Spring JDBC DAO abstraction layer offers a meaningful exception hierarchy for managing the exception handling and error messages thrown by different database vendors.
与竞争的数据库供应商的考试相比，IBMDB2考试似乎很少有过于具体的 “追求细节” 类型的问题，而更多的问题都需要 “深入的思考”。
Compared to competing database vendors' exams, the IBM DB2 tests seem to have fewer overly specific trivial pursuit questions and more questions requiring deep thought.
在这种情况下，您在IBMCognosBI中为数据库供应商实例创建一个IBM Cognos bi数据源，并拥有对其中的所有架构的访问权。
In IBM Cognos BI, in this scenario, you can create one IBM Cognos BI data source for the database vendor instance and have access to all schemas within it.
参照参考资源的jdbcTest链接或数据库供应商产品文档，查找您具体数据库提供商的相关设置(特别是jdbcurl和jdbcdriver的值)。
Refer to the JDBC Test link in Resources or to your database vendor's product documentation to find the Settings (specifically, the jdbcurl and jdbcdriver values) for your specific database vendor.
应用程序所发送的消息由应用程序服务器（Application Server）进行处理，并使用SQL和数据库供应商特定的XA调用发送给数据库。
The messages sent by the application are processed by the Application Server and forwarded to the database using SQL and database vendor specific XA calls.
要将两个目录之间的联接向下推到数据库供应商，只需将这两个ContentManagerDataSource属性指向同一个IBMCognosbi数据源名称。
To push the join between the two catalogs down to the database vendor, simply have both Content Manager data source properties point to the same IBM Cognos BI data source name.
开发环境不会只包含来自一个供应商的数据库，一个组织中的应用程序不会只使用一个单一数据库访问方法。
Development environments rarely comprise databases from a single vendor, and applications in an organization rarely use a single database access methodology.
甲骨文是世界上最大的类似的数据库的专利软件供应商——实际上的购买商，享有的市场份额达到了近50%。
Oracle is the world's biggest vendor of "proprietary" (essentially meaning "paid for") software to run such databases, with a market share of nearly 50%.
在处理期间，会触发一个事件(因为在LUW执行期间该订单提交到了数据库)，自动向供应商发送消息补充该项的库存。
During processing, an event is fired (because the order is committed to the database during the LUW) to send a message automatically to the supplier to restock that item.
同样的，要实现确定供应商库存交付准确性用例，我们需要从StoreOrders和Logistics数据库中抽取数据。
Similarly, to implement the Determine Supplier Stock Delivery Accuracy use case we need to extract data from the Store Orders and Logistics databases.
比如雀巢在200个国家出售超过十万种产品，有55万家供应商，但由于数据库一团糟它并未形成强大的采购议价优势。
Nestlé, for example, sells more than 100, 000 products in 200 countries, using 550, 000 suppliers, but it was not using its huge buying power effectively because its databases were a mess.
比方说，雀巢（Nestlé）公司，在200个国家销售超过10万种产品，拥有55万个供应商，但该公司过去却因为其数据库乱得一塌糊涂而无法有效利用其巨大的消费群。
Nestlé, for example, sells more than 100,000 products in 200 countries, using 550,000 suppliers, but it was not using its huge buying power effectively because its databases were a mess.
幸运的是，在整个Behemoth中，这些数据库是一致的，由于Behemoth在市场中的规模，因而它能够“推动”供应商按照Behemoth的意愿行事。
Luckily these databases are consistent throughout Behemoth; because of its size in the marketplace Behemoth is in a position to "motivate" its suppliers to work according to Behemoth's wishes.
由于该数据库是php之外的，所以将使用数据库抽象模块，其职责是为PHP中各种不同的特定于供应商的数据库函数提供同类接口。
Because this database is external to PHP, you'll use a database-abstraction module with the responsibility of providing a homogeneous interface to PHP's different vendor-specific database functions.
相反，那些仅使用JDBC核心功能的应用程序需要访问特定供应商的实现细节(例如，数据库连通性url)来连接数据源。
By contrast, applications that use only the core facilities of JDBC need access to vendor-specific implementation details (database connectivity URLs, for example) to connect to datasources.
JoinRowSet似乎允许的另一个有趣的功能是跨数据(甚至可以是不同供应商提供的数据库)执行离线join操作。
An interesting capability that the JoinRowSet seems to allow is the ability to perform offline JOIN operations across databases (even of different vendors).
RationalDataArchitect可以自动或手动发现数据资产(表中的列)之间的关系，这些数据资产可来自不同的数据库，甚至可以来自不同供应商的数据库。
Rational data Architect can discover relationships automatically or manually between data assets (columns in tables) across databases, even different databases from different vendors.
据悉，买家数据库将得以逐步细分，以发挥不同买家数据对不同茶叶供应商的服务与增值需求。
It is learned that the buyer will be a gradual breakdown of the database in order to play different buyers on different data suppliers of tea services and value-added demand.
据悉，买家数据库将得以逐步细分，以发挥不同买家数据对不同茶叶供应商的服务与增值需求。
It is learned that the buyer will be a gradual breakdown of the database in order to play different buyers on different data suppliers of tea services and value-added demand.
应用推荐