Data Migration Methodologies -- FoxPro to Access
From: Koronis Rift <foo_at_bar.com>
Date: Thu, 22 Aug 2002 09:34:20 -0400
Message-ID: <um9q2tn9da9ude_at_corp.supernews.com>
(Crossposted to: comp.databases.theory, microsoft.public.access.conversion) "Avoid Data Migraines During Data Migration", Christine Raker and Robert
Knowlton
Date: Thu, 22 Aug 2002 09:34:20 -0400
Message-ID: <um9q2tn9da9ude_at_corp.supernews.com>
(Crossposted to: comp.databases.theory, microsoft.public.access.conversion)
Am just beginning to undertake a rather large[1] data migration/data conversion project, moving from an off-the-shelf customer information system to a custom-built one. Current system uses Visual FoxPro (appx. 230 tables), new system uses Access 97 (appx. 80 tables).
The Problem: New database was designed "from scratch", solely from the enterprise data model. The existing database schema was not evaluated at all for the purposes of migrating the legacy data to the new system. Thus, my question.
Any tips, links, articles, white papers, jokes, war stories, etc... would be greatly appreciated! (No need to crosspost replies, I'll track the thread in both newsgroups)
-- [1] Well, not huge databases -- but large in the sense that it's just myself and a contractor working on the migration. -- Koronis Rift "Reply To" Address Will Not Work Just Use The Newsgroup And Have A Nice DayReceived on Thu Aug 22 2002 - 15:34:20 CEST