Migrating a Visual FoxPro Database to a SQL Database

• patel.shashank702 18199

  SSC Veteran

  Points: 253

  More actions

  June 22, 2011 at 7:13 am

  #239648

  Dear Sir,

  I wanna to Migrating a Visual FoxPro Database to a SQL Database.

  kindly suggest me any possible tool or methods.

  awaiting for ur response

  thanks

  Shashank Patel

• Orlando Colamatteo

  SSC Guru

  Points: 182276

  More actions

  June 25, 2011 at 4:55 pm

  #1344158

  patel.shashank702 18199 (6/22/2011)

  ---

  Dear Sir,

  I wanna to Migrating a Visual FoxPro Database to a SQL Database.

  kindly suggest me any possible tool or methods.

  awaiting for ur response

  thanks

  Shashank Patel

  http://blogs.msdn.com/b/sqlcat/archive/2008/01/25/foxpro-to-sql-server-migration-experience.aspx

  As an aside, regarding you comment "awaiting for ur response", we know 🙂 but we're all unpaid volunteers answering questions on our own time for the sake of learning and helping people. If you need something in a hurry look into hiring someone.

  There are no special teachers of virtue, because virtue is taught by the whole community.
  --Plato

• Welsh Corgi

  SSC Guru

  Points: 116520

  More actions

  June 26, 2011 at 12:26 pm

  #1344236

  You can use the upsize wizard from Visual Fox Pro.

  Here is a link on how to do this: http://msdn2.microsoft.com/en-gb/library

  For better, quicker answers on T-SQL questions, click on the following...
  http://www.sqlservercentral.com/articles/Best+Practices/61537/

  For better answers on performance questions, click on the following...
  http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

• Rich Mechaber

  SSChampion

  Points: 11130

  More actions

  June 27, 2011 at 2:06 pm

  #1344804

  I went through a conversion of this nature, changing a 15-year-old FoxPro database into MySQL. This database ran a mid-size company, with around 2-4 million transactions in it.

  I opted to use pass-through queries from FoxPro to load the data into MySQL. This allowed me to write everything in one interface (FoxPro), so I could use FoxPro to first execute cleanup tasks, searches, re-formatting, etc. before the data was copied over. Yet, the pass-through queries meant I could execute queries on the new database server to run the INSERTs and UPDATEs.

  I'm not sure I'd do it that way again. The link someone else posted above suggested exporting to tab-delimited files from FoxPro and then importing into SQL Server. My approach had no middle steps to it. But the performance was slow my way. Since it was a one-time conversion, I wasn't too interested in tuning it for faster performance: my critical concern was accuracy and completeness of the migration.

  YMMV.

  Good luck,

  Rich