具有百万行的日志表。怎么办？ [英] Log table with millions of rows. Now, what?

问题描述

我有一个包含数百万行的日志表。我正在考虑将数据分成多个表（即LoginHistory，ExceptionHistroy，PaymentProcessingHistory等）当使用具有许多行（不是列）和创建多个表的大表时，使用什么术语？

I have a Log table with millions of rows. I'm thinking about separating the data into multiple tables (i.e. LoginHistory, ExceptionHistroy, PaymentProcessingHistory, etc.) What is the term used when taking a large table with many rows (not Columns) and creating multiple tables?

我当前的日志表模式类似于：LogID，LogMessage，LogReason，LoggedBy，LoggedOn等。

My current Log table schema resembles: LogID, LogMessage, LogReason, LoggedBy, LoggedOn, etc.

太多东西在一张桌子，我想？

The problem is I'm putting too many things in one table, I think? Perhaps the table is too generic?

感谢

推荐答案

Sharding 是术语de jour。从链接：

Sharding is the term de jour. From the link:

水平分区是一种数据库设计原则，数据库表的行被分开保存，而不是按列分割用于归一化）。每个分区构成分片的一部分， 可能位于单独的数据库服务器或物理位置。

Horizontal partitioning is a database design principle whereby rows of a database table are held separately, rather than splitting by columns (as for normalization). Each partition forms part of a shard, which may in turn be located on a separate database server or physical location.

这篇关于具有百万行的日志表。怎么办？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！