blocks|key|3781473|text|通常情况下，最好将这些数据移动到独立的数据库(数据库仓库)中，并保持工作数据库的干净。在数据仓库中，您的数据可以保存多年，而不会影响您的应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3781474|参考:维基百科上的Data+Warehouse|offset|length|3781475|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Data_warehouse^0|0|9|E|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Usually it's better to move such data into seporate database (database warehouse) and keep working database clean. At data warehouse your data can be kept for many years without impacting your application.

Reference: <a href="http://en.wikipedia.org/wiki/Data_warehouse" rel="nofollow noreferrer">Data Warehouse</a> at Wikipedia

blocks|key|4626590|text|我一直在追问统治机构在寻找什么。例如，美国国税局希望你保留7年的历史，或者出于安全原因，我们保留3年的日志信息，等等。所以我猜你可以做两件事，确定你的数据的生命周期，我想3年就足够了，然后你可以添加is_deleted标志以及一个日期，这样你就可以标记一些数据来删除。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4626591|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I've always gone by what is the ruling body looking for. Example the IRS wants you to keep 7 years of history or for security reasons we keep 3 years of log information, etc. So I guess you could do 2 things, determine what the life span of your data is I would say 3 years would be enough and then you could add the is_deleted flag along with a date that way you would be able to flag some data to delete sooner than later.

blocks|key|4626659|text|Data+lives+forever...or通常都是这样的。一种常见的做法是记录有结束日期和/或开始日期。因此，对于你的whizbang，你有一个开始日期(这样它就不会出现在正式发布之前的销售报告中)和一个结束日期(这样它就会在生命周期结束后从报告中消失)。使用适当的日期作为报告和应用程序的标准，您将不会看到大爆炸，除非您应该在什么时候，并且数据仍然存在(理论上，它应该是无限的)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4626660|正如Koistya+Navin提到的，在某个时间点将数据移动到数据仓库也是一种选择，但这在很大程度上取决于您的“旧”数据有多大，以及您需要将其保持多长时间以供访问。|4626661|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Data lives forever...or often it should. One common practice is to have end and/or start dates for a record. So for your whizbang, you have a start date (so that it won't appear on sales reports before it's official launch), and an end date (so that it drops off of reports after it's been end-of-lifed). Using the proper dates as criteria for your reporting as well as your applications, you won't see the whizbang except for when you should, and the data still exists (which it should, theoretically infinitely).

As Koistya Navin mentions, moving data to a data warehouse at a certain point is also an option, but this depends in large part on how large your 'old' data is, and how long you need to keep it readily available for access.

blocks|key|561692|text|是的，所有数据都有生命周期。是的，它与您拥有的数据类型相关。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|561693|一些数据具有以秒为单位的寿命(例如身份验证令牌)，一些其他数据具有虚拟的永恒性(比存储数据的介质和格式更长，例如所有权记录)。|561694|您将不得不更具体地说明您正在设想的数据类型，或者在您自己的组织中进行一次普查，了解这些数据的通常使用期限。|561695|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Yes, all data has a lifespan. And yes, it is relative to the type of data you have.

Some data has a lifespan measured in seconds (authentication tokens, for instance), some other data virtual eternity (more than the medium and formats it is stored into, like for instance ownership records).

You will have to either be more specific as to the type of data you are envisioning, or do a census in your own organization as to the usual lifespan of stuff.

blocks|key|561714|text|我们独特的口味各不相同。我们有一些数据(绝大多数)会在3个月后过期(硬产品限制)，但可以在以后的任何日期恢复。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|561715|我们还有其他有效不朽的数据。|561716|在实践中，我们提供的大多数数据都是新鲜的，并且经常需要几周，最多一个月，然后才会零星使用。|561717|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Our particular flavor varies. We have some data (a vast majority) which goes stale after 3 months (hard product limit) but can be revived at any later date.

We have other data that is effectively immortal.

In practice, most of the data we serve up is fresh and frequently requested for a few weeks, at most a month, before falling to sporadic use.

blocks|key|561755|text|“大量死数据”是多少？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|561756|由于处理能力和数据存储如此便宜，除非有非常好的理由，否则我不会清除旧数据。您还需要考虑其法律含义。大公司(甚至是小公司)可能对旧数据有令人难以置信的长期保留政策，以便在被法官传唤时为自己节省数百万美元。|561757|我会向你们的任何法律部门查询，找出这些数据需要存储多长时间。这是最安全的赌注。|561758|此外，问问自己删除旧数据的好处是什么。唯一的好处是一个更整洁的数据库吗？如果是这样，我是不会这么做的。你会看到10倍的性能提升吗？如果是这样，我会这么做的。然而，这确实是一个复杂的问题，我们很难获得给你好的建议所需的所有信息。|561759|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

How much is "a lot of dead data"?

With processing power and data storage so cheap, I wouldn't purge old data unless there's a really good reason to. You also need to consider the legal implications. Large (and even small) companies may have incredibly long retention policies for old data, to save themselves millions down the road when they are subpoenaed for it by a judge.

I would check with whatever legal department you have and find out how long the data needs to be stored. That's the safest bet.

Also, ask yourself what the benefit of removing the old data is. Is the only benefit a tidier database? If so, I wouldn't do it. Are you going to see a 10X performance increase? If so, I'd do it. This really is a complex question though, and it's tough for us to have all the information required to give you good advice.

blocks|key|4626839|text|我有几个项目，客户想要所有的历史数据(追溯到19年前)。相当多的真正的旧数据是畸形的，并将成为导入新系统的噩梦。我们说服他们，他们不需要超过10年前的记录，但就像你说的，这一切都与你存储的数据类型有关。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4626840|顺便说一句，数据存储现在非常便宜，如果它不影响应用程序的性能，我会把它放在原处。|4626841|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I have a few projects where the customer wants all the historical data (going back over 19 years). Quite a bit of the really old data is malformed and is going to be a nightmare to import into the new system. We convinced them that they won't need records going back any further than 10 years, but like you said it's all relative to the type of data you're housing.

On a side note, data storage is extremely cheap right now, and if it isn't affecting the performance of your application, I would just leave it where it is.

blocks|key|4626868|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4626869|+...但可以肯定的是，所有数据都有某种生命周期？|blockquote|4626870|4626871|4626872|不是任何一种我们可以有意义地谈论的寿命。很多数据一旦创建或记录就毫无用处了。这样的数据可以立即丢弃，而不会产生任何影响。另一方面，一些数据具有足够的价值，它将比托管它的当前系统更持久。如果亚马逊完全更换他们目前的基础设施，他们存储的客户历史仍然是非常有价值的。|4626873|就像你说的，它是相对的。每种类型的数据都有自己的生命周期，与另一种类型的数据的生命周期无关。没有什么有意义的“数据的平均寿命”。|4626874|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|L|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|M|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|N|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|O|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|P|7|@]|8|@]|9|$]]|$1|H|3|I|4|5|6|Q|7|@]|8|@]|9|$]]|$1|J|3|-4|4|5|6|R|7|@]|8|@]|9|$]]]|K|$]]

<blockquote>
 [...] but certainly all data has some sort of life span?
</blockquote>

Not any kind of life span we can talk about meaningfully. A lot of data is useless as soon as it's created or recorded. Such data could be discarded immediately with no effect. On the other hand, some data has enough value that it will outlive the current system that hosts it. If Amazon were to completely replace their current infrastructure, the customer histories they have stored would still be immensely valuable.

As you said, it's relative. Each type of data has its own life span that has no relation to another type of data's life span. There's no meaningful "average life span of data".

blocks|key|3782294|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3782295|我有可能存放大量的死数据。(永远不会再访问的数据)。|blockquote|3782296|3782297|3782298|但当他们执行这些报告时，他们就会访问这些数据。|3782299|在此之前，您需要以某种形式保存数据。移动到另一张表，或者像您提到的那样切换。|3782300|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|L|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|M|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|N|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|O|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|P|7|@]|8|@]|9|$]]|$1|H|3|I|4|5|6|Q|7|@]|8|@]|9|$]]|$1|J|3|-4|4|5|6|R|7|@]|8|@]|9|$]]]|K|$]]

<blockquote>
 I have the potential of housing a lot of dead data. (data that is never accessed again).
</blockquote>

But they will when they perform those reports then they are accessing that data.

Until then you'll need to keep the data in some form. Move to another table or have a switch like you mentioned.

blocks|key|4626943|text|我们的许多客户将数据在线保存了2年。在此之后，它被转移到备份磁盘，但如果需要，可以将其置于在线状态。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4626944|考虑添加一列“过期”或“生效日期”。这将允许您将产品标记为过时，但如果满足时间范围，报告将返回该产品。|4626945|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Many of our customers keep data online for 2 years. After that it's moved to backup disks, but it can be put online if needed.

Consider adding a column "expiration" or "effective date". This will allow you mark a product as obsolete, but reports will return that product if the time range is satisfied.

blocks|key|561943|text|uh...at+oversimplifying...it的风险听起来像是使用DateDeleted而不是bit可以解决你的保存多久的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|561944|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

uh...at the risk of oversimplifying...it sounds like using DateDeleted instead of a bit would solve your how-long-to-keep issue.

Recently I’ve found myself in a database tangle where management wants the ability to remove data from the database, but still wants that data to appear in other places. Example: They want to remove all instances of the product whizbang, but they still want whizbang to appear in sales reports. (if they ran one for a previous date).

Now I can add a field, say is_deleted, that will track whether that product has been deleted and thus still keep all my references, but over a period of time, I have the potential of housing a lot of dead data. (data that is never accessed again). How to handle this is not my question. 

I’m curious to find out, in your experience what is the average life span of data? That is, on average how long is data alive or good for before it gets either replaced or deleted? I understand that this is relative to the type of data you are housing, but certainly all data has some sort of life span?

What is the life span of data?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

最近，我发现自己陷入了数据库的混乱之中，管理人员希望能够从数据库中删除数据，但仍然希望这些数据出现在其他地方。例如:他们希望删除产品whizbang的所有实例，但他们仍然希望whizbang出现在销售报告中。(如果他们在之前的约会中运行了一个)。现在我可以添加一个字段，比如is_deleted，它将跟踪该产品是否已被删...

问数据的生命周期是多少？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问数据的生命周期是多少？EN