Question

2
Replies
226
Views
PaigeR11 Member since 2014 6 posts
United Health Group
Posted: 3 years ago
Last activity: 3 years ago
Closed

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 SR Exists
Moderation Team has archived post
Share this page LinkedIn