The decision on whether I should split the table

Question

I create a website with several languages

I have a description table that contains descriptions of each product and a column indicating the language. Therefore, it contains a string for each language description

Now I am concerned that I have different types of products in the system, and reading the description of any product will have to go through this table. This means that a lot of traffic to this table

Is there any gain in creating several description tables that will be devoted to certain product groups and distributing the number of calls to this separate table into several tables?

Will this bring me a performance boost in Microsoft SQL?

Answer 1

For practical purposes, no. If the table is correctly indexed, you should not see the difference.

You should not prematurely optimize the database structure.

Answer 2

How many products are you talking about? Because if it is less than 10 million, don't even bother optimizing it that way.

What you are talking about is basically a separation scheme. This is used for really large data sets. Less than 10 million do not come close, although each element is massive.

If what you do reads a lot, few write that there is no benefit from this kind of splitting.

Do not try to optimize the problem until you have a problem.

Answer 3

:

• ? , .
• ( )?

, . - , , , , , .

Answer 4

. , , , . , , .

, .

Answer 5

Agreed - I prefer to solve problems that are actual problems.

If your application is modular enough and your data access level is well structured, this should not be a problem for sharing things later. If you use stored procedures, views, etc., to abstract the basic structure of tables from the application, performing such optimization at a later date, should have minimal impact on your source.