DATA MODERNIZATION
10 Day – OLTP Data workload to Azure database Migration Pilot
10 Day Pilot – OLTP Data Workload To Azure Database Migration
Background
Organizations want to leverage the power and flexibility of cloud for databases to eliminate end of life concerns, reduce cost, pay-as-you go features, improve security and business agility.
Organizations are hesitant to take the leap to modern data cloud due to uncertainties related to migration cost, ever extending timelines of migration, data loss concerns, lack of skilled people.
Success Criteria
Ability to migrate an identified database workload(This can be identified during the workshop) from On-Premises to Azure database as per the plan without cost overrun.
Data to be migrated with the least amount of/no disruption to the application.
Automate the data validation process once all the data is migrated to the Azure database and ensure there are no gaps.
Our Offering
Acuvate proposes to do a 10-day pilot for OLTP database migration to Azure.
Acuvate as part of its data migration and modernization offering would be using its custom data migration framework and Optimum as an accelerator for schema generation and post migration validation.
Acuvate would do end to end migration and demonstrate the ability to scale the framework to the entire data landscape using Microsoft and Acuvate’s migration accelerators.
10 Day Pilot – OLTP Data Workload To Azure Database Migration
- Assess and Identify a small business critical OLTP data workload that can be migrated to Azure.
- Objects to be migrated (Maximum possible)
- 2 transaction tables.
- 10 dependent master tables.
- 10 dependent object scripts(SPs, functions, views)
- Execute SSMA and/or Optimum tool to generate the assessment report.
- Formulate migration strategy and resolve blockers
- Execute schema, data and code migration to Azure database.
- Validate migrated objects and data.
- Document Azure data migration plan with scalability
- One Power BI operational report with maximum of six chart controls and three filters.
- Any changes to the schema or database objects of the source system.
- Any issues with data or data quality.
- Environment setup and configuration.
- Any documentation not mentioned in scope
- Any custom development for the migration.
- Performance optimization.
- Maintenance, support and cost optimization.
- Business and technology stakeholders would be available to help understand the business-critical data workload and to identify the objects to be migrated.
- Acuvate team would have access to the necessary infrastructure resources for data migration to both source systems and destination system.
- Infrastructure setup would be done as soon as the business kick off is complete.
- Acuvate will be leveraging migration tools by Microsoft or Acuvate’s proprietary tools and accelerators during the migration.
- All project activities would be done from Acuvate’s offshore development centers in India.
10 Day Pilot - Data Migration Approach
ASSESS
(Day 1 and Day 2)
- Execute tools, generate migration readiness report
- Analyse reports to identify possible issues and blockers
- Propose resolutions to identified issues/threats
DEFINE
(Day 3 and Day 4)
- Define Migration Strategy
- Prioritize objects to be Migrated
- Execution plan for Migration Including History and Live data migration
MIGRATE
(Day 5 to Day 8)
- Migrate schema and data to target environment
- Leverage OPTIMUM for schema & data migration
- Leverage CODE PATTERN BOOK for code migration
VALIDATE
(Day 9 and Day 10)
- Leverage scripts generated by Acuvate framework to perform data validation
- Execute the feeds both on Source & Target to validate Code Migration
- Evaluate Results
Deliverables
- Readiness Report
- Solution to Issues
- Migration Strategy
- Cutover Plan
- Migrated Scripts for Testing
- Test Results
- Operational report
- Azure Data migration plan
Trusted by the best
