Add a new Data Hub

Manuela_Apostol

What are best practices when is needed to create a new Data Hub due to workspace space limitation to 130GB? 

 

I have already built the Data Hub which contains historic data and data validation processes. I still need to load further years. The only option I have, without deleting the data already loaded is to create a new Data Hub model on a different workspace and feed the models from both DHs.

 

I am aware of best practices, why Anaplan should not be a DW, but besides this, I am sure there are clients which are using multiple Data Hub due to space limitation of one workspace and I would like to know the challanges and best practices on setting this up. 

 

Thank you! 

JaredDolich

@Manuela_Apostol  before you add another workspace, and if you haven't already done so, you might consider reading @rob_marshall data hub for peak performance and @DavidSmith planual starting at page 54. I had the same problem with a client. Once I implemented DISCO I cut my module space down 40% simply by dimensionalizing time in my transaction files. I also moved the text line items that parse the UID to a separate module and used it as a control module. This took out another 20%. With flat modules the size you're talking about every line item should be heavily scrutinized - avoid text if you can.

 

If you've attempted all these and are committed to building a new workspace, you might also consider using ALM to keep the models in sync. ALM won't affect the data, just the structure. You can implement ALM across workspaces - just remember the target model must have the most recent revision tag in the source model. I've done this once before and only had two issues. First, I had to reset all the import data sources when I moved the model to a different workspace. Second, ALM is a model level migration, not an object level.

 

Just some ideas for you.