What is the design idea of User profile database?

We want to establish a database for user profile analysis. the main information is the user's personal information, order information for the purchased items, and order transaction amount. Now I want to export the data, store it in the database again, and perform a profile analysis. However, I want to store 100,000 of the data in a table... we want to establish a database for user profile analysis. the main information is the user's personal information, order information for the purchased items, and order transaction amount.

Now I want to export the data, store it in the database again, and perform profile analysis. However, if I put hundreds of thousands of data records in a table, the response is too slow, however, if multiple data tables are stored separately based on the item type, many fields need to be spliced in Association query.

I just got started and thought too simple. please give me some advice on how to store databases.

Reply content:

We want to establish a database for user profile analysis. the main information is the user's personal information, order information for the purchased items, and order transaction amount.

Now I want to export the data, store it in the database again, and perform profile analysis. However, if I put hundreds of thousands of data records in a table, the response is too slow, however, if multiple data tables are stored separately based on the item type, many fields need to be spliced in Association query.

I just got started and thought too simple. please give me some advice on how to store databases.

The definition of stored fields should be similar to that of the quantity. The table should be indexed and defined, and data can be obtained and analyzed in different data segments. At present, most companies adopt this method.

How large is the data volume of 100,000? Not found in 1 ms