Results 1 to 2 of 2
  1. #1
    Join Date
    Oct 2008

    Unanswered: Large Tablel Question

    I am running SQL Server 2005 , Service pack 2. We have a table that is 16 gb with 270 million rows. Right now there aren't too many issues with performance but this table is expected to grow to double the size within the next 6 months. I have run the database tuning advisor against data derived from SQL profiler but there have been no additional index recommendations. I am reluctant to place additional indexes on the table anyway because we have 6 non-clustered and 1 clustered indexes on the table already.
    Do you think it would be a good idea to look at something like table partitioning for this table to keep performance at top speed? Or would you recommend some other action?


    Rebecca Johnston
    DBA - SQL Server

  2. #2
    Join Date
    Jul 2003
    San Antonio, TX
    Sounds like a good candidate for partitioning and archiving. Is all the data being accessed, or there is a cutover identifier that may be used to determine which portion can be archived/moved out/switched out?
    "The data in a record depends on the Key to the record, the Whole Key, and
    nothing but the Key, so help me Codd."

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts