blocks|key|189956|text|如果所有数据都是相同的，就不要将其拆分到不同的表中。看一下Oracle的表分区。按区域(或更多)拆分的150个(或更多)分区可能更符合您要查找的内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|189957|我还建议您查看Oracle+Database+Performance+Tuning+Tips+&+Techniques一书，并浏览Oracle网站上的Ask+Tom。|189958|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|$]]

If all the data is the same, don't split it in to different tables. Take a look at Oracle's table partitions. One-hundred fifty partitions (or more) split out by region (or more) is probably more in line with what you're going to be looking for.

I would also recommend you look at the Oracle Database Performance Tuning Tips &amp; Techniques book and browse Ask Tom on Oracle's website.

blocks|key|2600060|text|只有15M行？其实不是很多..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2600061|使用一个表；解决如何在150个表中编写一个150路联合将是一件很糟糕的事情。|2600062|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|$]]

Only 1.5 M rows? Not a lot really...

Use one table; working out how to write a 150-way union across 150 tables will be murder.

blocks|key|3970665|text|150万行看起来并不是很多。在任何给定的时间点，有多少人正在访问表？你有什么索引设置吗？如果你希望它变得更大，你可能想看看partitioning+in+databases。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3970666|FWIW，我经常使用数据库处理100M%2B行。它不应该这么糟糕，除非你有成千上万的人同时使用它。|3970667|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Partition_%2528database%2529^0|1P|P|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

1.5 million rows doesn't really seem like that much. How many people are accessing the table(s) at any given point? Do you have any indexes setup? If you expect it to grow much larger, you may want to look into <a href="http://en.wikipedia.org/wiki/Partition_%28database%29" rel="nofollow noreferrer">partitioning in databases</a>.

FWIW, I work with databases on a regular basis with 100M+ rows. It shouldn't be this bad unless you have thousands of people using it at a time.

blocks|key|3970730|text|每个区域一张表是不规范的；你可能会在那里损失一大堆效率。每个数据录入站点一张表也是很不寻常的。规范化是巨大的，它将为您节省大量的时间，所以我会确保您没有存储任何重复的数据。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3970731|如果您使用的是oracle，则不需要有多个表。它将支持超过150万行的数据。如果您需要加快数据访问速度，可以尝试使用雪花模式来引入经常访问的数据。|3970732|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|$]]

1 table per region is way not normalized; you're probably going to lose a bunch of efficiency there. 1 table per data entry site is pretty unusual too. Normalization is huge, it will save you a ton of time down the road, so I'd make sure you're not storing any duplicate data.

If you're using oracle, you shouldn't need to have multiple tables. It'll support a lot more than 1.5 million rows. If you need to speed up data access, you can try a snowflake schema to pull in commonly accessed data.

blocks|key|687978|text|如果您指的是表中的1,500,000行，那么您就没有太多需要担心的了。Oracle可以轻松地处理比这更大的负载。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|687979|如果您需要识别数据传入的区域，您可以创建一个Region表，并将其中的ID绑定到大数据表。|687980|IMHO，你应该发布更多的细节，我们可以更好地帮助你。|687981|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|$]]

If you mean 1,500,000 rows in a table then you do not have much to worry about. Oracle can handle much larger loads than that with ease.

If you need to identify the regions that the data came in, you can create a Region table and tie the ID from that to the big data table.

IMHO, you should post more details and we can help you better.

blocks|key|2600088|text|有2,000行的数据库可能会很慢。这完全取决于您的数据库设计、索引、键，最重要的是运行数据库服务器的硬件配置。您的应用程序使用此数据的方式也很重要。读密集型数据库还是事务密集型数据库？你现在问的问题没有正确的答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2600089|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|$]]

A database with 2,000 rows can be slow. It all depends on your database design, index, keys and most important is the hardware configuration your database server is running on. The way your application uses this data is also important. Is a read intensive database or transaction intensive? There is no right answer to what you are asking right now.

blocks|key|2600104|text|您首先需要考虑哪些操作将访问表。如何执行插入？是否会更新现有行，如果是，更新方式是什么？这些行将增长多少，其中有多少百分比将增长？行会被删除吗？用什么标准？您将如何选择数据？根据什么标准，每个查询有多少个？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2600105|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|$]]

You first need to consider what operations are going to access the table. How will inserts be performed? Will the existing rows be updated, and if so how? By how much will the rows grow, and what percentage of them will grow? Will rows get deleted? By what criteria? How will you be selecting data? By what criteria and how many per query?

blocks|key|3970749|text|数据分区可用于大于15M行的数据量。研究优化SQL查询、批处理和数据存储。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3970750|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|$]]

Data partition can be used for volume of data much larger than 1.5m rows. Look into optimizing 
the SQL query ,batch processing and storage of data.

I have over 1.500.000 data entries and it's going to increase gradually over time. This huge amount of data would come from 150 regions. 

Now should I create 150 tables to manage this increasing huge data? Will this be efficient? I need fast operation. ASP.NET and Oracle will be used.

Database design question: How to handle a huge amount of data in Oracle?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我有超过1.500.000个数据条目，而且随着时间的推移，它将逐渐增加。这些海量数据将来自150个地区。现在，我是否应该创建150个表来管理这些日益增长的海量数据？这会有效率吗？我需要快速手术。将使用ASP.NET和Oracle。

问数据库设计问题:如何在Oracle中处理海量数据？
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问数据库设计问题:如何在Oracle中处理海量数据？EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问数据库设计问题:如何在Oracle中处理海量数据？
EN