How to design the statistical tables of various data in the CRM system?

The company is doing a CRM system. There is a lot of data in the statistics that need to be recorded in the database.
For example, record each employee's number of customers per day, track the number of records, whether the number of customers per day, tracking the number of records is the standard.
The current scenario is two:
1. These statistics are recorded in a single table.
2. Each statistic is recorded separately in a single table.
Don't know that way better? Or is there another better, more complete way to implement it?
Have you ever done this kind of function of the great God, give some advice, in this extremely grateful

Reply content:

The company is doing a CRM system. There is a lot of data in the statistics that need to be recorded in the database.
For example, record each employee's number of customers per day, track the number of records, whether the number of customers per day, tracking the number of records is the standard.
The current scenario is two:
1. These statistics are recorded in a single table.
2. Each statistic is recorded separately in a single table.
Don't know that way better? Or is there another better, more complete way to implement it?
Have you ever done this kind of function of the great God, give some advice, in this extremely grateful

Suggest the background to open the timing statistics

If considering the later data volume is larger, it is recommended to put separately in each table, because the late data volume, the table is to be split, it is better to split up now. Don't forget to build related indexes.

