Scenario I have a table of 10 million rows. I divide it into 10 sections, which leads to 1 million lines for each section, but I do nothing (for example, move sections to different file groups or spindles)
Will I see a performance increase? Is this really like creating 10 small tables? If I have queries that perform key searches or crawls, will performance increase as if they were working with a much smaller table?
I am trying to understand how partitioning differs from having a table with a well-indexed table and where it can be used to improve performance.
Would a better scenario move old data (using partition switching) from a primary table to a read-only table?
Has a table with 1 million row section and 9 million rows, analogues (in performance) to move 9 million rows to another table and leaving only 1 million rows in the original table?
source
share