Outline of High Speed Ingestion with Data Partitioning in Content ...
Outline of High Speed Ingestion with Data Partitioning in Content ... Outline of High Speed Ingestion with Data Partitioning in Content ...
© Copyright 2007 EMC Corporation. All rights reserved.16“Global” indexes span the entire set of partitionsSELECT …. FROM … WHERE OBJECT_NAME = ‘FOO’Faster lookup’s than Non-partition KeyLocal ones, but maintenance cost is high
© Copyright 2007 EMC Corporation. All rights reserved.17Index notes• A partitioned set of Documentum tables will only leveragelocal indexes– Partition exchange can’t be done with a table that has a global index• Limits on partitions:– Oracle : 64K – 1 partitions per table/index– SQL Server 2005: 1000 partitions per table/index• Non-partition key lookups will get more expensive as thenumber of partitions grows– However, parallel index scans over partitions possible
- Page 4 and 5: © Copyright 2007 EMC Corporation.
- Page 6 and 7: © Copyright 2007 EMC Corporation.
- Page 8 and 9: © Copyright 2007 EMC Corporation.
- Page 10 and 11: © Copyright 2007 EMC Corporation.
- Page 12 and 13: © Copyright 2007 EMC Corporation.
- Page 14 and 15: © Copyright 2007 EMC Corporation.
- Page 18 and 19: © Copyright 2007 EMC Corporation.
- Page 20 and 21: © Copyright 2007 EMC Corporation.
- Page 22 and 23: © Copyright 2007 EMC Corporation.
- Page 24 and 25: Partition ExchangeDmr_content_rDmr_
- Page 26 and 27: © Copyright 2007 EMC Corporation.
© Copyright 2007 EMC Corporation. All rights reserved.16“Global” <strong>in</strong>dexes span the entire set <strong>of</strong> partitionsSELECT …. FROM … WHERE OBJECT_NAME = ‘FOO’Faster lookup’s than Non-partition KeyLocal ones, but ma<strong>in</strong>tenance cost is high
Change language