Once there is an understanding about how the data is being used, both in terms of overall workload and data warehouse usage, the next step is to record that information in the context of user activity. When aspects have been identified, the development of the road-map for moving the data can begin. A holistic approach to creating the road-map for data movement would be to:
Identify the workload(s) that need to be moved
Scope out how to move that workload
Understand how the different applications and databases are connected to each other
Determine architectural investments that need to be made
Develop road map
It is necessary to understand that optimizing data warehouse needs to be done iteratively – again and again – because data is dynamic and changes over time. Data that is identified as hot one month/year may be considered warm or cold next month/year.
It is vital that to understand how it is used, both in terms of the workload and in terms of the capacity that in the data warehouse. To successfully rebalance the data warehouse, the first step is to access and identify less-frequently accessed data and resource-intensive workloads.
