用于连接数据库的数据库驱动器。
驱动程序层显示花费在执行数据库驱动器处理逻辑上的时间。
The driver layer shows times spent performing database driver processing logic.
在我们的场景中，所使用的系统在磁盘驱动器、目录结构、数据库驱动程序位置等方面都是完全相同的。
In our scenario, the systems we are using are identical in terms of disk drives, directory structure, database driver location, and so on.
降低磁盘资源争用的另一种可行办法是将信息传递引擎数据表和日志移动到文件系统中其他更快的驱动器上，或者使用远程消息传递数据库。
Another possible way to reduce disk contention is to move the messaging engine data tables and logs to separate, faster drives on the file system or use a remote messaging database.
如果因为磁盘驱动器或RAID故障而造成数据库不可访问，就不能进行故障转移。
If the database is inaccessible because the disk drive or RAID set is down, failover cannot occur.
在硬盘驱动器上找到一个用于存储数据库的位置。
Find a location on your hard drive where you want to store your database.
还可以定义其他数据库所需的新驱动器以便连接到其他非ibm数据库。
You can also define new drivers for other databases needed to make connections to other non-IBM databases.
SOA/BPM生产数据库的典型数据库大小（就磁盘上的占用空间而言）是良好性能所需的空间（就磁盘驱动器数量而言）的一小部分。
The typical database sizes (in terms of occupied space on the disk) for SOA/BPM production databases are a small fraction of the space (in terms of number of disk drives) needed for good performance.
本文中的示例都是基于UNIX的，但也可以将它们用于基于Windows的数据库(除了数据库路径支持的驱动器符号外)。
The examples that are used throughout this article are UNIX-based. However, they should still apply to Windows-based databases (except that only drive letters are supported for database paths).
DB _ PATH：必需参数，表示数据库最初创建的路径或驱动器(Windows)。
DB_PATH: This is a required parameter that represents that path or drive (on Windows) on which the database was originally created.
驱动器文件是数据库厂商提供的数据库JDBC 驱动器jar 文件。
The driver files are the database JDBC driver jar files provided by database vendors.
这样确保ApplicationServer可以通过数据库提供的驱动器连接到数据库上。
This is to ensure that Application Server can connect to the database through the drivers supplied by the database.
测试数据库位于另一个名为DBServer 的机器中，而数据库连接是JDBC，使用了特定于数据库的驱动器。
The test database is located in another machine called DB Server, and the database connection is JDBC using a database-specific driver.
确保为驱动器选择了Type4，并确保将数据库名称更改为实际的数据库名称(在我们的示例中是ISSWBPE)。
Make sure that you select Type 4 for the driver and that you change the database name to your actual database name (in our example: ISSWBPE).
这意味着甚至数据库的小部分都可以从高速低能的光纤驱动器迁移到低速高能的SATA驱动器上。
This means that even subsections of databases can be migrated from high-speed, low-capacity Fibre Channel drives to lower-speed but higher-capacity SATA drives.
每一个定义了数据库的路径(或者Windows中的“驱动器”)中都有一个本地数据库目录。
A local database directory resides in each path (or "drive" for Windows) in which a database has been defined.
依赖于数据库管理系统和JDBC驱动器的实现，该操作会根据应用程序服务器的时区将时间戳数据写到数据库中。
Depending on the database system and the implementation of the JDBC driver, this usually results in timestamp data written in the time zone of the application server.
当你增加数据库连接或者改而使用支持多线程的JDBC驱动器时，单例模式能够很容易地适应这一变化。
If you add database connections or use a JDBC driver that allows multithreading, the singleton can be easily adjusted to allow more connections.
该系统总共有112个磁盘驱动器可用于数据库。
In total, there are 112 disk drives in the system for the database.
诸如ibmsoliddb之类的内存中缓存解决方案将数据库从相对较慢的硬盘驱动器转移到相对较快的RAM，大大提升响应速度。
In-memory caching solutions such as IBM solidDB move the database off of relatively slow hard drives into relatively fast ram, dramatically improving response time.
无效的路径。检查数据库的目录。-SDF文件在本地驱动器C。
The path is not valid. Check the directory for the database. - SDF file is in the local drive - C.
我会同时显示将文件保存到硬盘驱动器，并在接下来的章节中的数据库。
I will show both saving the file to hard drive and to a database in the next sections.
数据库和事务日志文件必须在驱动器发生故障时受到保护。
The database and transaction log files must be protected in the event of a drive failure.
通常数据库使用一个简单的RAID1的非常快(和低容量)SAS驱动器(10 - 15 krpm)，至少在索引上。有时你把数据放在较慢(便宜)磁盘，RAID 1,5或6。
Usually DBs use a simple RAID1 of very fast (and low capacity) SAS drives (10-15krpm), at least for the indexes. sometimes you put the data on slower (and cheaper) disks, on RAID1, 5 or 6.
通常数据库使用一个简单的RAID1的非常快(和低容量)SAS驱动器(10 - 15 krpm)，至少在索引上。有时你把数据放在较慢(便宜)磁盘，RAID 1,5或6。
Usually DBs use a simple RAID1 of very fast (and low capacity) SAS drives (10-15krpm), at least for the indexes. sometimes you put the data on slower (and cheaper) disks, on RAID1, 5 or 6.
应用推荐