数据库规范化是否仍然必要？

本文介绍了数据库规范化是否仍然必要？的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

数据库规范化仍然是东西？

当我在数据库课程学习时，我们教会了所有级别的规范化，并说我们必须

现在，所有 NoSQL <

解决方案

这取决于什么类型的应用程序，

对于OLTP应用程序（主要是数据输入，具有许多INSERT，UPDATE和DELETES以及SELECT），归一化通常是一件好事。 p>

对于OLAP和报告应用程序，规范化没有帮助。 SELECT查询将对非标准化模式运行得更快，这可以通过视图实现。

您可能还会在这些非常受欢迎的类似问题中找到一些有用的信息： p>

我应该标准化我的数据库

在数据库方面，正规化正确性，反正规化性能是一个正确的口头禅？

规范化数据库对资源的影响是什么？

如何确保某人正常化数据库？

是否真的更好使用归一化表？

Is database normalization still "the thing?"

When I studied during a databases course we were taught all levels of normalization and were said that we must always do it.

Now, with all the NoSQL movement, it seems normalization is no longer the thing to do?

解决方案

It depends on what type of application(s) are using the database.

For OLTP apps (principally data entry, with many INSERTs, UPDATEs and DELETES, along with SELECTs), normalized is generally a good thing.

For OLAP and reporting apps, normalization is not helpful. SELECT queries will run much more quickly against a denormalized schema, which could be achieved with views.

You might also find some helpful information in these very popular similar questions:

Should I normalize my DB or not?

In terms of databases, is "Normalize for correctness, denormalize for performance" a right mantra?

What is the resource impact from normalizing a database?

How to convince someone to normalize a database?

Is it really better to use normalized tables?