Contents
- 1 How do you validate data after migration?
- 2 Which type of testing is necessary when project is migrated from one platform to another?
- 3 Which of the given activity must be performed in order to test database migration?
- 4 How are supplementary systems verified during data migration?
- 5 Are there any scenarios specific to SQL server migration?
- 6 When do you need pre data migration testing?
How do you validate data after migration?
Here are 8 steps to follow in the data migration process.
- Define the Scope.
- Study requirements, Business Rules and Mapping Document.
- Dependencies and Interactions.
- Create Test Cases and Queries to Verify the Data.
- Execute Test Cases.
- Compare the Results.
- Non-Functional Testing.
- Functional Application Test.
Which type of testing is necessary when project is migrated from one platform to another?
Performance testing is important to ensure that migration to new system/software has not degraded the performance of the system. It is also required to carry out Load and stress tests to ensure the system stability.
Which of the given activity must be performed in order to test database migration?
Testing Activities here will be:
- Analyzing requirements and identifying the stable requirements.
- Analyzing the scope of testing.
- Analyze and test all the flows in legacy application against the new application.
- Test the new flows in the migrated application if any.
What are the risks of data migration?
Data Loss Risk During the data migration process, data loss can occur. When the data is migrated to the new system or target system, some of the data may not migrate over from the source system. This risk can be evaded by conducting data migration testing.
Can a sampling method be used for Migration validation?
It should be noted that although sampling is an effective method of migration validation, it is by definition based on an inherent level of accepted risk. This means that you cannot ensure that 100% of the data will be migrated without error.
How are supplementary systems verified during data migration?
Supplementary systems are identified and verified to work with the destination system, and source system test cases will need to be converted for use with the destination system post migration. During the post migration testing phase, the number of records in the source and destination systems will first need to be compared.
Are there any scenarios specific to SQL server migration?
These include scenarios that are specific to SQL Server to SQL Server migration (older versions to newer versions), as well as foreign platform (such as Oracle, DB2, MySQL and Sybase) to SQL Server migration. Applies to: SQL Server to SQL Server migration.
When do you need pre data migration testing?
During the migration testing process, pre-data migration testing is vital for complex data structures, although it may not always be necessary for simple data structures. Firstly, the source data will need to be tested against the requirements of the destination system, using source-to-destination mappings.