Paige Robinson (PaigeR11)
United Health Group
Paige Robinson
United Health Group
PaigeR11 Member since 2014 7 posts
United Health Group
Posted: September 27, 2017
Last activity: September 29, 2017
Posted: 27 Sep 2017 14:55 EDT
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***

Data Integration Support Case Exists
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.