You'll have to hit a particular database quite a bit.
您需要经常与一个特定的数据库打交道。
Quite often, modifying data in one database table requires a data synchronization with other types of databases that are in different locations.
通常情况下，在一个数据库表中修改数据要求与不同位置的其他类型的数据库保持数据同步。
Database queries can become quite intense on their own, often pegging a CPU at 100 percent for doing simple SELECT statement with reasonable size datasets.
数据库查询自身可以变得相当激烈，通常在对大小合理的数据集执行简单的SELECT语句时限定在100%的CPU。
Such a polarization is quite powerful considering the fact that you might have multiple applications trying to interact with the same database.
如果考虑到有多个应用程序都将与同一个数据库进行交互，您就会发现这种分化是非常强大的。
If we had to reset a database to a known state before each unit test, the tests would be quite complex and certainly would run slower than we desire.
如果我们需要在每次单元测试前将数据库重新设置到一个已知状态，那么测试会相当复杂并且运行速度自然会比我们期望得要慢。
As it turns out, the application has since become quite popular for studying activity on the company database.
但结果是，它变成了研究公司数据库活动的相当流行的应用程序。
The cluster directory database on a different cluster within the same domain contains quite different information.
同一域内其他集群的目录数据库包含完全不同的信息。
Matching work partitions to their data partitions will increase the probability of a cache hit within the server and decrease remote accesses to the database, which introduces quite a bit of latency.
将工作分区与它们的数据分区进行匹配，这将增加服务器缓存的命中概率，并减少对数据库的远程访问，后者会引起较大的延迟。
Good relational database practitioners and object model designers can have competing goals that make their respective implementations quite different from each other.
优秀的关系数据库人员和对象模型设计者可能具有相互竞争的目标，从而使得其各自的实现也具有很大的差异。
On the other hand, if you're working with a huge data set (data mining, or database operations), having access to a much larger data cache may quite easily make up for this.
另外一方面，如果您要处理大量数据集(数据挖掘或数据库操作)，访问更大的数据缓存，那么对于64位模式来说这非常容易。
Luckily, as Pramod Sadalage and I show in refactoring Databases, 1 it's quite straightforward to implement database refactorings manually.
幸运的是，如PramodSadalage和我在重构数据库中所描述的，1手动实现数据库重构是非常直接的。
The robust set of functions provided by DB2 Express-C compares quite favorably to community editions of database programs offered by other vendors.
与其他厂商提供的数据库程序社区版本相比，DB2Express-C 提供的功能是相当慷慨的。
Myriad steps could be taken to improve this aspect, from database sequences to a framework like Hibernate, which handles IDs quite elegantly.
在这方面有多种改进方法，从数据库序列到像Hibernate 这样的框架都可以，Hibernate 框架用于相当得体地处理ID。
As I showed, db4o offers quite a few more ways to query than your typical relational database can, giving you a range of options for dealing with various application scenarios.
正如我所说的那样，与通常的关系数据库相比，db4o可以提供更多的方法来进行查询，为您处理不同应用程序场景提供了更多选择。
Clearly, arriving at the best design can be quite an intensive effort, so the time it takes can only be justified if the database performance must be the best possible. As a rule.
很显然，实现最佳的设计可能需要花费大量精力，并且仅当数据库性能必须可能是最佳时才能证明设计是最佳的。
However, a program computing the number of keystrokes required to change one phrase into the other would say that those sentences are quite different, and may not offer translations from the database.
但是，计算将一个短语转换成另一个短语所需击键次数的程序会说这两个句子完全不同，不可能从数据库中提供翻译。
The model is quite simple at this point of my application; there is only one table in the database for products and a product has the four properties I mentioned earlier.
模型在我的应用程序中十分简单，数据库中只有一个用于产品的表，而一个产品有我前面提到的四个属性。
Our example requires a database connection to start, nothing else, and for this, the SAMPLE database will do quite nicely.
例子只要求一个数据库连接来启动操作，不要求其他任何东西，对此，SAMPLE数据库将表现得非常出色。
And, as new products and new product attributes are introduced over time, the database schema (and any applications that depend on it) would need to be altered, which can be quite costly.
另外，随着时间的推移会出现新的产品和新的产品属性，就需要修改数据库模式（以及依赖于它的所有应用程序），这会导致很高的成本。
So there are quite a lot database failures and events that you can catch this way.
所以，用这种方式可以捕捉很多数据库故障和事件。
Even though we've cleaned it some, the database code is still full of ugly special cases and not-quite-successful attempts to introduce generality.
尽管我们已经清理了数据库代码，但仍然存在一些令人不愉快的特殊情况，以及试图引入一些共性的不太成功的尝试。
The logic behind such a backup script is quite simple: obtain a list of tables from the database, iterate over this list and use commands such as DESC?
这类备份脚本背后的逻辑很简单：从数据库取得一个表列表，迭代此列表并使用如DESC ？
Connecting to a source database (for example, Oracle) is quite easy.
连接到源数据库(例如oracle)非常容易。
It is quite easy to grant a user all database permissions and authorities using the Control Center, as is shown in Figure 1.
通过使用ControlCenter，很容易为一个用户授予所有数据库许可和权限，如图1所示。
As you can see, the database is quite straightforward: words have a one-to-many relationship with definitions and synonyms.
如您所见，这个数据库非常直观：word与definition和synonym具有一对多的关系。
For example, the database schema is something that can likely wait for quite a long time.
例如，数据库模式(schema)可以等待很长时间。
The virtual portion is quite expandable by the database server and can be paged out to disk by the operating system.
虚拟区可以通过数据库服务器得到较大扩展，并且可以通过操作系统将虚拟区页移出(page out)磁盘。
I think it's quite unusual to intentionally design a database this way nowadays, so it's likely you'll only need to create composite keys where it is a long-established practice.
我认为，如今故意以这样一种方式设计数据库的做法并不常见，您只需要在符合惯例的场合创建组合键。
Optimization of a macro-database application system is a quite complex job.
大型数据库应用系统的性能优化是一项非常复杂的工作。
Rising antivirus software are quite good in these aspects, can master the Rising antivirus software, virus database update, the effective use of antivirus software antivirus antivirus is the key.
瑞星杀毒软件在这些方面都相当不错，能够熟练掌握瑞星杀毒软件使用，及时升级杀毒软件病毒库，有效使用杀毒软件是防毒杀毒的关键。
应用推荐