VFP: Importing VFP data into SQL Server


I’ve written an article outlining How to use SQL Server 2005 Integration Services (SSIS) to import Visual FoxPro data into SQL Server.

The article is reasonably basic and covers:

  • Using SQL Server Business Intelligence Development Studio to create the package and manage errors
  • Using SQL Server Management Studio to create the Integration Service
  • Using SQL Agent job to schedule it
  • Gotchas (including UNC mapping, and the VFP OLE DB driver)
  • Brief overview of a real world implementation using SSIS
  • Brief discussion of SSIS versus VFP Upsizing Wizard

The article is 49 pages long, but don’t be alarmed, most of it is screen shots. It is available in Word or PDF format. I’ve included the Word format in case you want to edit the article, add your own comments, copy stuff out etc.

Download PDF: [drain file 1 url] ([drain file 1 size])

Download Word: [drain file 2 url] ([drain file 2 size])


  • Thanks for the article… I know that this will help so much to my conversion from VFP tablest SQL Sever…
    I let you know if it works already… again, thanks in advance. From CDO,Phils.

  • Gracias por el Articulo…Yo tengo una base de datos muy grande que esta VFP 9 y necesito migrarlo a SQL con toda su estructura y data …ojala que este articulo sea de gran ayuda..soy nuevo en FOXPRO

  • Un consulta investigando encontré que se debe desistanlar los CTP Para la instalación del SEDNA.,,quisiera saber que es un CTP?..esperare su pronta respuesta gracias

  • Hello… Thanks for the step by step explaination.

    I was doing this for importing fox por tables into SQL Server 2008 R2.

    When I do this, I figured out that the import will also returned records marked as DELETED in the fox pro tables. I would like to know how can I avoid the deleted records which are appearing as normal records on my SQL server database.

    Any help would be appreciated.


    • Farhan, are you able to do a PACK and REINDEX on your FoxPro tables? This will remove all the deleted records from FoxPro, and then you can do the import into SQL. If you’d rather not remove them all, then you may need to copy to intermediate FoxPro tables, PACK and REINDEX those and then import.

  • Hi Craig – thanks for the doc. I’ve got a situation now where after running the SSIS package any blank date fields in my VFP database are now populated with 12/30/1899 in the new SQL database that is created by the package. Any way to stop that happening (I’d rather they were left blank during the import). Thanks!

    • Hi Steve. Sorry, it’s been a long time since I’ve worked with SQL and VFP, so I’m not in a position to really help with this. But leaving your comment here in case any other readers can chime in with thoughts.