Hi champs,
Can you any one throw their ideas on how the following can be verified (data base testing)
Requirement
content migration testing need to be verified
Explanation:
We are migrating from old website to New CMS system. Old website uses the databse MYSQL and new website uses the data base SQL server. So we need to verify all the records in the old database has been migrated to SQL server properly
Cheers,
Sattu
You can independently generate similar SQL scripts for both databases and then compare results against them. Depending on the nature of the data (either being extremely important that it matches or it is OK if some of the data can be fixed later) you will write more or less SQL scripts.
Basically what you are doing is performing an Independent assessment to make sure that the Developers migration scripts from MYSQL to SQL server worked correctly.
Think of it as corner testing, and again depending on the nature of the data, you work in from the corners until you have a high confidence level that your migration scripts worked correctly.
You could also use an automation tool like QTP or whatever to help facilitate a speedy test and results comparison.
-Erik
It kinda depends what you want to validate.
If you just want to make sure all the data came over roughly then do a row count per table on the source, then the same on the destination on the move.
Now that doesn't help you make sure the right data made it over. For that you could do some sort of row checksum but be careful as different precision on data can cause a problem.
Those are the easy 2. It gets much harder if you want to start testing security access, or query plans, especially as the 2 are so different.
The other way to do all this would be to test the database through the app itself, I'd do the first 2 in addition thogh.
Thanks champs
Basically extracting data from the mysql and SQL server is a good option. But our data schema has modelled in complex structure so extracting the data by writing the new sql server query is not an easy task in our case, and also in this QTP is a best option to use if we are allowed to write independant SQL scripts.
Is there any other way i.e, with out writing the SQL queries and comparing the front end data with the old webpages
I have tried with getroproperty() in QTP to extract the old website content and new website content (front end) it has worked upto some extent, but i have to write a number of Recovery scenarios to get rid of the exceptions that occur while executing.
Please suggest another way if possible.
-SATTU
When migrating data from one db to another you can check on row counts etc for prelim check. For a detail check use data transformation techniques to pull data out of source and destination tables where you have a doubt and verify these using diff techniques of any other parser that you may have.
There is no shortcut if you have Gbs of data that you need to verify.
thanks,
