|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Yesterday @ 6:11 PM
Points: 231,
Visits: 1,073
|
|
We have a table with almost 2 billion rows and we have partitioned this table based on date. The size of the table including indexes is 1.6 TB( 600 data + 1TB index). We have 14 indexes on this table. Recently a developer tried to query this table and got timed out issue because he was using the fields not in indexes. He was trying to pull last 3 months data.
My question over here is how to maintain these indexes on this partitioned table? Is it good to seperate the old partitions(switch) into archive tables and add new partitions ? What's the best way to maintain this table?
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 5:54 AM
Points: 37,726,
Visits: 29,985
|
|
The entire point of partitioning is ease of archiving and easier maintenance. It's not a performance tuning technique.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP 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
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Yesterday @ 6:11 PM
Points: 231,
Visits: 1,073
|
|
Thanks Gila.
We are not archiving this table. Just adding rows to it which is causing more issues. As the table is growing bigger and bigger. So as said in my previous comment just switch the old partitions into individual archive tables.
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 5:54 AM
Points: 37,726,
Visits: 29,985
|
|
Or switch them into a partioned archive table and maybe merge the partitions.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP 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
|
|
|
|