Question
UnitedHealth Group
US
Last activity: 29 Sep 2017 16:15 EDT
History_Work table partitioning
Our HISTORY_WORK table has grown extremely large after just 3 months in production. As a mitigation measure we would like to partition the table by pxhistoryforreference and create a local index. We are using Microsoft SQL server. Microsoft SQL Server does not have partition by hash capabilities. What are recommendations for partitioning the HISTORY_WORK table in Microsoft SQL Server?
Date is not a good candidate as it is not used in the where clause and would not provide benefit.
***Moderator Edit: Vidyaranjan | Updated SR details***
Pegasystems Inc.
US
Look at this article for recommendations for partitioning on different databases
https://docs-previous.pega.com/database-management/pegarules-table-partitioning
UnitedHealth Group
US
We are considering using the below approach for partitioning our History_Work table.
Does anyone have thoughts based on the below?
Partition by pxHistoryForReference
UPMC-CLMS-WORK- C10 - anything beginning with C-10 will fall into this partition
UPMC-CLMS-WORK- C11 - anything beginning with C-11 will fall into this partition
UPMC-CLMS-WORK- C12 - anything beginning with C-12 will fall into this partition
This pattern would be followed through C-99