score:2

Accepted answer

That depends on your access patterns. Do you often need to access data from multiple partitions at once? Then you should probably combine them.

Anyway, development is probably easier when you only have one table (without one-to-one joins). If there is no particular reason to split them, combine them.

Attention: I think there is a column limit in SQL Server.

You can expose subsets of the columns by creating indexes. Each index would be set on the ID column with an arbitrary subset of columns as "included" columns. This will leave the choice to the optimizer. It will choose the best possible way. It can also join between indexes so you are in a total win situation that way.

Recommendation: Combine the tables into one and create one index for each table you previously had.


More questions

More questions with similar tag