I don't mean the whole thing. Pick some output that your applications usually produce and see if you can get the same results for both databases.
I am not saying that this is the only and best way, just in addition to the mentioned sample approach. If you want to know for sure you will have to write an application that checks this for you, even if it runs for a while On 6/4/07 12:31 PM, "paulizaz" <[EMAIL PROTECTED]> wrote: > > What do you mean by "same output" ? > > I have too much data to go through and check if all the data is the same. > This is my problem. Sampling would speed this up, but I need something more > accurate. > All data is important. > > > > > Olaf Stein-2 wrote: >> >> Besides the sample approach, output data (a set you would output on a live >> system anyway) from both db setups and see if you can get the same output >> from both >> >> Olaf >> >> >> On 6/1/07 10:35 AM, "paulizaz" <[EMAIL PROTECTED]> wrote: >> >>> >>> Hi all, >>> >>> I have somebody creating a C# class to migrate data from one SQL database >>> to >>> another slightly differently structured SQL database. >>> >>> Please can anybody suggest ways to verrify that the data has migrated >>> successfully, in whole and acurrate?? >>> >>> I feel a sample approach would not quite be substancial. >>> I want to keep it seperate from the migration process itself (having my >>> person write a verification script may also not work as he will be using >>> the >>> same thought processes and knowledge that he used for the migration) >>> >>> Free Software, scripts, utilities, packages, industry approaches?? >>> >>> Sorry Im no Tech wizzard, Any ideas appreciated..................... >> >> >> -- >> MySQL General Mailing List >> For list archives: http://lists.mysql.com/mysql >> To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] >> >> >> -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
