What should be the best strategy for partitioning?

  • Hi,

    I have tables as follows:

    teams

    (

    school_sport_id int primary key,

    school_name varchar(100),

    city

    ....

    ....

    sport_id ,

    school_id

    );

    events

    (

    event_id int primary key,

    event_name

    start_date_time datetime

    ...

    ...

    );

    event_participants

    (

    event_participants_id int primary key

    school_sport_id int

    ....

    ....

    );

    Records in tables:

    teams = 1552502

    events = 3915918

    event_participants = 8464728

    Now I want to create partition on these tables.

    My application queries data from these tables based on specific season and sports.

    It defines 4 School SEASON in a year.

    For example,

    Records for 2012 FALL Cricket.

    List of teams in a school.

    What should be the best strategy for partitioning?

    Please suggesst me.

  • What is the reason for partitioning these tables?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Application are working very slow. We created indexes as required, but still we found it slow.

  • Then don't waste your time looking at partitioning, it's not a performance-related tool.

    Please post table definitions, index definitions and execution plan, as per http://www.sqlservercentral.com/articles/SQLServerCentral/66909/ and we'll see what we can suggest in terms of useful indexes

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Could you please give me an idea for how many rows I should go for partition?

  • Again, don't waste your time considering, designing or implementing partitioning if your goal is to make queries faster. It won't help much, if at all. Partitioning is not for performance, it's for maintenance and fast loads/deletes of data.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

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

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