OLTP
abbr. 联机事务处理
2026-03-21 23:27 浏览次数 22
abbr. 联机事务处理
oltp dataoltp数据库
OLTP DatabaseOLTP数据库
Web OLTP联机事务处理
Global OLTP全局OLTP
OLTP platformOLTP平台
OLTP Applications在线交易处理软件
OLAP OLTP区别点
oltp平台OLTP platform
With these tips, you can get your OLTP application up and running with reasonably good performance.
有了这些技巧,就可以启动自己的OLTP应用程序并使其拥有非常好的运行性能。
Suppose a table in an OLTP database already has 6 or 7 indexes. Would I give a thumbs-up to adding another?
假设OLTP数据库中的一个表已经拥有6 个或7 个索引,我还会赞成再添加一个吗?
The testing that is described demonstrated that EFDs provide a substantial improvement (approximately 9X) in I/O performance when used in an OLTP database environment.
所讨论的这个测试说明了 EFD用在一个OLTP数据库环境时能大大提高I/O性能(约为9倍)。
For OLTP applications, it is very important to place the log files on a separate physical device where their high activity will not negatively impact other work on the same hard disk drive.
对于OLTP应用程序,将日志文件放置在单独的物理设备上是极其重要的,因为这样它们的频繁活动就不会给在同一硬盘驱动器上的其他工作带来不良影响。
Considering the data growth in the last decade, OLTP servers are also handling a massive amount of data that demands an optimal tool for performing extract, transform, and load (ETL) operations.
鑒于十年以来的数据增长,OLTP服务器现在也在处理大规模数据,这就需要一个优化工具来执行提取、转换和加载(etl)操作。
In Table 1 you can see a breakdown of the differences between OLTP and OLAP databases, with particular regard to access patterns and resource usage for each type.
在表1中,您可以看到OLTP和OLAP数据库间差异的细目,这些差异主要与每种技术使用的访问模式和资源使用情况相关。
Finally, the clustering of the data is guaranteed and cannot become un-clustered, as is normally the case in OLTP systems.
最后,数据的集群受到保障,数据不会又变成非集群状态,在OLTP系统中就常常会出现这种情况。
This paper describes a number of DB2 performance fundamentals, tuning tips and techniques, and major DB2 configuration parameters that can affect OLTP performance.
本文描述了一些DB 2性能方面的基本要素、调优技巧和技术以及可能影响OLTP性能的一些主要的DB2配置参数。
Because the only table may be the hotspot unless it is partitioned, OLTP Systems typically don「t work well with it.
除非进行分区,否则唯一的数据表会成为热点,OLTP系统通常在这方面都不太好。
With its dynamic multi-threading architecture, IDS scales well and can manage very large volumes of data, providing high performance in the OLTP environment.
IDS 采用动态的多线程架构,具有很好的可伸缩性,可以管理非常大量的数据,在OLTP环境中提供高性能。
On OLTP systems, where user sessions are performing quick queries, tuning this parameter can be very important.
在OLTP系统上,用户会话执行快速查询,调节此参数可能非常重要。
Batch and query applications typically do a lot of sequential processing, while data access for OLTP tends to be more random in nature.
批处理和查询应用程序通常要进行大量的顺序处理,而用于OLTP的数据访问往往更具有随机性。
For OLTP applications, there should be less sorting and temp space required and only a handful of concurrent cursors opened at a time.
对于OLTP应用程序,所需的排序和临时空间会比较少,一次只打开少数并发游标。
OLTP applications should not be performing large sorts.
OLTP应用程序不应该执行大型排序。
However, there are still some situations where choosing static SQL makes sense, involving security considerations, and maximizing performance for certain OLTP workloads.
然而,仍然有一些适合静态SQL的情形,比如涉及到安全性因素、针对某些OLTP工作负载最大化性能等情况。
This is especially important in the OLTP environment where transactions are huge and query response time is critical.
这在OLTP环境中尤为重要,该环境中的事务十分巨大,而且查询响应时间十分关键。
For each step, we」ve listed some key V8.2 enhancements that apply to OLTP databases, where the primary interest is in indexes.
对于每一步,我们列出了V8.2中适用于OLTP数据库(其中最相关的就是索引)的一些关键的增强。
An OLTP environment is a database environment that facilitates and supports transaction-oriented workloads, which typically consist of numerous data entry and retrieval operations.
OLTP环境指的是使用和支持面向事务的工作负载的数据库环境,它一般由许多数据实体和查询操作组成。
In the first test, we sequentially inserted 100,000 documents with and without indexes, committing after every document as many OLTP applications would.
在第一个测试中,我们顺序插入100,000个具有或不具有索引的文档,像许多OLTP应用程序那样在每个文档之后提交。
This is especially true in an OLTP environment, where transactions are huge and data is constantly inserted, deleted and updated.
OLTP环境中尤其如此,该环境中的事务十分巨大,并且不断地要插入、删除和更新一些数据。
What if you know your OLTP searches should use the same execution plan for different binding values?
要是你知道你的OLTP搜索对不同绑定值应该使用相同执行计划又该怎么办呢?
OLTP databases contain transacations at the most granular level.
OLTP数据库包含最细粒度级别的事务。
The database queries in TPC-H are more complex than typical OLTP queries.
TPC- H中的数据库查询要比典型的OLTP查询更加复杂。
In any real OLTP database, implementing this change can be a problem.
在任何真实的OLTP数据库中,实现此更改可能是一个问题。