• RID Index: Yes my all in one partition is...

    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    |--Nested Loops(Inner Join, OUTER REFERENCES:([Bmk1000], [Expr1007]) WITH UNORDERED PREFETCH)

    |--Index Seek(OBJECT:([VCUWarehouse].[dbo].[share_jc3].[idx_Share_Mbr]), SEEK:([VCUWarehouse].[dbo].[share_jc3].[DL_LOAD_DATE]='2014-05-21 00:00:00.000'), WHERE:([VCUWarehouse].[dbo].[share_jc3].[CLOSED]=(0)) ORDERED FORWARD)

    |--RID Lookup(OBJECT:([VCUWarehouse].[dbo].[share_jc3]), SEEK:([Bmk1000]=[Bmk1000]) LOOKUP ORDERED FORWARD)

    So in the absense of indexing a large chunk of the relevant 240 columns ... I can either ditch the partitions, or deal with poor query performance for non-index mentioned colums?

    Would partitions in SQL 2008 behave the same?