为什么我们需要一个时态数据库？

问题描述

我正在阅读关于时态数据库，似乎他们已经建立在时间方面。我不知道为什么我们需要这样一个模型？

与正常的RDBMS有什么不同？我们不能有一个正常的数据库，即RDBMS，并说有一个触发器将时间戳与发生的每个事务相关联？可能会有性能打击。但我仍然怀疑在市场上有强大案例的时态数据库。

现有的数据库是否支持这样的功能？

$ b $时间数据库有效地存储数据的时间序列，通常通过具有一些固定的时间尺度（例如秒或甚至毫秒），然后仅存储在时间序列中的变化。测量数据。 RDBMS中的时间戳是每个测量的离散存储的值，这是非常低效的。时间数据库通常用于实时监控应用程序，如SCADA。一个成熟的系统是来自OSISoft的PI数据库（）。

I was reading about temporal databases and it seems they have built in time aspects. I wonder why would we need such a model?

How different is it from a normal RDBMS? Can't we have a normal database i.e. RDBMS and say have a trigger which associates a time stamp with each transaction that happens? May be there would be a performance hit. But I'm still skeptical on temporal databases having a strong case in the market.

Does any of the present databases support such a feature?

解决方案

A temporal database efficiently stores a time series of data, typically by having some fixed timescale (such as seconds or even milliseconds) and then storing only changes in the measured data. A timestamp in an RDBMS is a discretely stored value for each measurement, which is very inefficient. A temporal database is often used in real-time monitoring applications like SCADA. A well-established system is the PI database from OSISoft (http://www.osisoft.com/).

这篇关于为什么我们需要一个时态数据库？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！