SQL Server Performance

split a table?

Discussion in 'Performance Tuning for DBAs' started by mtmingus, Oct 7, 2003.

  1. mtmingus New Member

    I have a table contains data for different nodes (~100).
    Each node contains records anywhere from a few thausands to
    a million. Each node program is interested in its own
    data only. Even though I have a combo clustered index on this
    table, is it a good idea to split this table into
    pieces, each piece will contain data for only one node,
    each piece (table) will be created on the fly by the
    program? Thanks!
  2. Luis Martin Moderator

    ...created on the fly by the program?.
    Mean auxiliars tables?



    Luis Martin

    ...Thus mathematics may be defined as the subject in which we never know what we are talking about, nor whether what we are saying is true.
    Bertrand Russell
  3. mtmingus New Member

    Once a specific Node is created by the program,
    this table can be created as well, by executing
    a stored proc.

    quote:Originally posted by Luismartin_ar@yahoo.com

    ...created on the fly by the program?.
    Mean auxiliars tables?



    Luis Martin

    ...Thus mathematics may be defined as the subject in which we never know what we are talking about, nor whether what we are saying is true.
    Bertrand Russell
  4. WaterBlue New Member

    The table should be split into pieces.And you need create some views for query.
    Add appropriate constraint,(SQL query tune can use this constraint)


    Work hard but no reward

Share This Page