“脏数据”的生成方法与干净数据的生成方法类似。
It was generated using an approach similar to the approach used to generate the clean data.
它并不等于fsync函数——也不是请求同步脏数据。
It is not equivalent to fsync — it's not a request to sync dirty data.
数据库读写器(DBWr)——异步地将缓冲区的脏数据写到物理数据文件中。
Database Writer (DBWr) - Writes to physical data files the dirty bits of buffer asynchronously.
合并意味着如果相同的记录被更新,或者在缓冲区内被多次标记为脏数据,则只保证最后一次更新。
Conflation means if the same record is updated or dirtied multiple times within the buffering period then it only keeps the last update.
文中提出了基于改进ART2网络的脏数据辨识与调整模型。
A model for dirty data identification and justification is put forward based on the modified ART2 network.
脏数据处理的过程就是对于含有脏数据的负荷曲线模式的辨识过程。
The process of dirty data processing is the recognition process of load curve pattern containing dirty data.
高速缓存中包含脏数据,但由于某些虚拟磁盘丢失或将转为脱机,因此无法将高速缓存的数据写入磁盘。
The cache contains dirty data, but some virtual disks are missing or will go offline, so the cached data can not be written to disk.
随着时间的推移,劳动力市场信息系统产生了大量的“脏数据”,降低了数据准确性和系统服务的质量。
Some "Dirty data" will appear in labor market information system after some time. It affects data accuracy and quality of system services.
因为同步变量使用他们自己内部的标识记录脏数据状态,在属性设置函数中设置脏位会引起递归调用问题。
Because SyncVars use properties internally to mark themselves as dirty, setting them dirty inside property functions could lead to recursion problems.
一个写线程释放一个锁之后,另一个读线程随后获取了同一个锁。本质上,线程释放锁时会将强制刷新工作内存中的脏数据到主内存中,获取一个锁将强制线程装载(或重新装载)字段的值。
In essence, releasing a lock forces a flush of all writes from working memory employed by the thread, and acquiring a lock forces a (re) load of the values of accessible fields.
理想情况下,多个线程不能同时访问同一块数据,脏读将不复存在,死锁则会被自动监测和处理。
Ideally no two threads can try to modify the same piece of data at the same time, dirty reads are not possible, and deadlocks are automatically detected and handled.
这些数据将初始化事务表、脏页表和打开文件表,以便它们能够用于恢复过程。
This data initializes the transaction table, dirty pages table, and open file table so they can be used in the recovery process.
如果有丢失数据或脏(dirty)数据,您的客户是否可以在数据源中进行纠正呢?
If there is any missing data or dirty data, can your customer correct this in the data sources?
不过有一个例外,对于“脏(dirty)”表空间中的long型字段和大型对象数据,总是需要进行备份。
The exception is for long field and large object data in "dirty" table Spaces, which are always backed up.
流作用域的持久化上下文对象将流期间加载的数据作为持久化实体来管理并将数据变更缓存为实体的脏状态。
The flow-scoped persistence-context object manages data loaded during the flow as persistent entities, and data changes cached as the entities' dirty states.
相反,在缓存中一旦进行更新操作,缓存就会跟踪脏记录列表,并定期将当前的脏记录集刷新到数据库中。
Instead, updates occur in the cache, the cache tracks the list of dirty records and periodically flushes the current set of dirty records to the data store.
SQL 2005有一个 基于快照的隔离级别 ,它能在不允许“脏读”的情况下避免数据读取阻塞数据写入,或者数据写入阻塞数据读取。
SQL 2005 has snapshot-based isolation levels that prevent readers from blocking writers or writers from blocking readers without allowing dirty reads.
SQL 2005有一个 基于快照的隔离级别 ,它能在不允许“脏读”的情况下避免数据读取阻塞数据写入,或者数据写入阻塞数据读取。
SQL 2005 has snapshot-based isolation levels that prevent readers from blocking writers or writers from blocking readers without allowing dirty reads.
应用推荐