It is not so easy to shift your home from one place to other.It is so costly and yes enough risky process.How many of you can really shift each of your belongings from your old place to your new place without a single item being missed or broken?The count may be in the binary digits. Same is the case with my new project the ‘DATA MIGRATION’.
Problems found:
1) Have to import a character whose ASCII value is greater than 255 and SQL SERVER 2005 supports only till 255.
2) Unicode characters are not properly recognized and hence duplicates are being inserted into the SQL Server database.
3) Some data is missing in the application,but seen in the database. Reason: Column name has been changed in the database but not in the existing migration scripts.
4) No debugging option given in SQL Server 2005. Solution: Create a Temp Table and check the correctness of data. (But is it possible to check every piece of data?)
5) Package suddenly gets corrupted and yes I have imported data till yesterday using the same package but today it is not working. Reason: Should be explored in the coming week.Solution: Luckily had a backup of the package.
These are the five key problems which really made me black and blue this week.
Thanks & Regards,
MrSharma56.
–“TESTING HAS BECOME MY PASSION OVER MY PROFESSION”
Note: Kindly suggest me even for the spelling & grammar mistakes (if any) present here.
This is a strange thing to see information about DATABASE in ur Blog…I have most Expected in testing View…
Data Migration Involves risk of Foreign Key Relation Ships and Integrity Constraints. When we r in the Migration, Backup file is a tool always to be prefereed,if BAKUP file is Corrupted in any means, Then QUESTION should be Raised to client or Project Lead who could help you in this Regard.
Master Table always should not be disturbed,Transaction tables are need to maintained with interrelated columns.
Any how, IF any Error Comes then
goto PAVANKISHORE@INTEQSOLUTIONS,
BCOZ, this felow is HEADING a lot ISSUES in DATA migration.
This is a strange thing to see information about DATABASE in ur Blog…I have most Expected in testing View…
Data Migration Involves risk of Foreign Key Relation Ships and Integrity Constraints. When we r in the Migration, Backup file is a tool always to be prefereed,if BAKUP file is Corrupted in any means, Then QUESTION should be Raised to client or Project Lead who could help you in this Regard.
Master Table always should not be disturbed,Transaction tables are need to maintained with interrelated columns.
Any how, IF any Error Comes then
goto PAVANKISHORE@INTEQSOLUTIONS,
BCOZ, this felow is HEADING a lot ISSUES in DATA migration.
