Table partitioning

  • Hi,

    I've a table with 1.000.000 rows where active records and inactive records are kept, since the user can search on both status (only 5% or less of the time they search inactive records). The inactive records are about 30% of the entire table.

    Is it worth creating a partition on the isActive column to "split" the data or adding a filter on the main indexes should be enough?

    Thanks,

    Pedro



    If you need to work better, try working less...

  • I don't think you'll gain anything from partitioning. I'd add the column to indexes. Partitioning is really for maintenance not performance, although you do get some performance from partition elimination.

  • PiMané (9/30/2016)


    Hi,

    I've a table with 1.000.000 rows where active records and inactive records are kept, since the user can search on both status (only 5% or less of the time they search inactive records). The inactive records are about 30% of the entire table.

    Is it worth creating a partition on the isActive column to "split" the data or adding a filter on the main indexes should be enough?

    Thanks,

    Pedro

    If you are looking for a performance boost, partitioning probably won't help. I'd start off with one or more filtered indexes.


  • Thanks, that what I thought also...

    And right now the column has 90% active and 10% inactive so for 99% of the cases is almost a table scan..

    Thanks,

    Pedro



    If you need to work better, try working less...

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply