Databases Reference
In-Depth Information
●
How complex is your BI and analytics? A documented analysis of the BI and analytics process
and infrastructure is needed to complete the BI migration and determine the associated
complexity. If the BI or analytics process is the major reason for the reengineering, you need
to determine if just changing the BI and/or analytics process and its infrastructure will provide
the performance and scalability.
●
How complex is your security configuration? A critical component of the ETL and BI
infrastructure is the associated security configuration. Depending on the migration option, the
impact on the security infrastructure can be significant or minimal. If the impact of the security
changes is significant, it will impact the overall performance in the new architecture and
require extensive testing for the migration.
●
How mature is your documentation? Often an ignored aspect in the data warehouse or BI, if
your current state documentation is not updated and is legacy or dated, do not even step into
the migration or modernization of your data warehouse.
●
Cost-benefit analysis—consider the multiple perspectives discussed in this chapter and perform a
detailed cost-benefit analysis. The cost should include all the following details by line item:
●
Acquisition costs of new infrastructure
●
Acquisition costs of new data
●
Migration costs:
-
One-time labor costs:
a.
Consultants
b.
Nonemployee staff
-
Ongoing labor costs:
a.
Consultants
b.
Employees
c.
New hires
●
Maintenance costs of current state infrastructure
●
Retirement costs of current state infrastructure
●
Identification of pitfalls—conduct a detailed proof of concept (POC), which will provide the
opportunity to identify the pitfalls and the areas of concern that need further validation in terms of
reengineering or modernization. The pitfalls to verify include:
●
Memory performance
●
Disk architecture
●
Network architecture
●
Scalability of the overall infrastructure
●
Compression of data at rest
●
SQL optimization
●
SQL generation
●
Develop a robust roadmap for the program that will include:
●
Timeline for the migration
●
IT and business teams' skills and people requirements
●
Migration execution by subject area or application
●
Testing and deployment plan
●
Backup and recovery plan
●
Rollback plan in case of issues
●
Business continuity plan
