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***