converting dbf to SQL

[Bluejay07]

Hello,

What would be the best way to convert Visual Fox Pro databases to SQL 2003?

In SQL 2000, it was possible to export the VFP data to dbase format and inport the data using the wizard.

That doesn't seem to be an option any more.

Any help would be greatly appreciated.

If at first you don't succeed, then sky diving wasn't meant for you!

 

[markros]

Did you mean to say, SQL 2008 ?

You may try using Doug Hennig's SQLXMLBulkLoad tool:

http://doughennig.blogspot.com/2006/07/sqlxmlbulkload-rocks.html

PluralSight Learning Library

 

[bborissov]

This is a question to VFP forum, not to SQL Server one.
BTW there is no SQL 2003, it is 2005 or 2008.
And in the SSMS there is a Import wizard.
Also in VFP there is upsizing wizard.

Borislav Borissov
VFP9 SP2, SQL Server 2000/2005.

 

[ousoonerjoe]

If there's not a simple Import/Export option, then you could always dump to flat files and then import those. Otherwise, I would recommend creating an application to convert the data. This would give you the control to scrub and verify the data as you move it to the new database. Any records not meeting your criteria is written to a separate table for further review and clean up. It will also help you in identifying any orphan records and weeding those out from the import. It takes time, but the end result is a much cleaner and accurate database to work with.

--------------------------------------------------
Bluto: What? Over? Did you say "over"? Nothing is over until we decide it is! Was it over when the Germans bombed Pearl Harbor? No!
Otter: Germans?
Boon: Forget it, he's rolling.
--------------------------------------------------

 

[Bluejay07]

Thanks for the responses.

@bboriisov, I would think this is as much an issue in the SQL forum as it would be in the VFP forum. Especially since the final product will be in SQL, not fox pro.

I will verify with the client as to the SQL version. As for the wizard (referencing 2005), it doesn't seem to have any datasource that I can use (as mentioned dBase IV was previously used and worked without any issues).

@ousoonerjoe, unfortunately I do not posses the knowledge to create a program for data conversion (plus the client will not pay for it).

It was relatively straight forward process in SQL 2000. I'm just looking for a similar approach.

If at first you don't succeed, then sky diving wasn't meant for you!

 

[ousoonerjoe]

It might seem to be an awkward way to get there, but why not use the 2000 Import/Export tools then convert it to 2005/2008?

Once you get it to SQL, you can convert it to practically any version you need at that point.

--------------------------------------------------
Bluto: What? Over? Did you say "over"? Nothing is over until we decide it is! Was it over when the Germans bombed Pearl Harbor? No!
Otter: Germans?
Boon: Forget it, he's rolling.
--------------------------------------------------

 

[Bluejay07]

I was thinking of doing it that way; however, that means I am converting the data.

The client's IT department are the ones to convert the data. The problem is that they upgraded their SQL version and no longer have SQL 2000.

Which is why I'm trying to find ways to help the out. They need their data converted to use the program I created for them.

If at first you don't succeed, then sky diving wasn't meant for you!

 

[bborissov]

You could download and install VFPOLEDB and use it as source for import.

But again this is more VFP forum than SQL Server
The that the final result will be SQL doesn't matter. You can't expect that the people that post here will have any knowledge about DBFs and esp. VFP.
And almost all problems that you will have during the conversion you must resolve in VFP not in SQL Server.

Borislav Borissov
VFP9 SP2, SQL Server 2000/2005.

 

[Bluejay07]

Thank you bborisov.

If at first you don't succeed, then sky diving wasn't meant for you!

 

[Bluejay07]

The version should be SQL 2005, not 2003.

If at first you don't succeed, then sky diving wasn't meant for you!

 

[Bluejay07]

@bborissov: do you forsee any problems with VFPOLEDB as the version of foxpro the client has is vfp6.



If at first you don't succeed, then sky diving wasn't meant for you!

 

[bborissov]

No.
VFPOLEDB should work fine with every versions of VFP.

Borislav Borissov
VFP9 SP2, SQL Server 2000,2005 & 2008.

 

[markros]

Use the latest VFPOleDB (version 9). There should not be problems using it with VFP tables of any version.

Also, you can use DTS with SQL Server 2005 (not with 2008). I believe I saw threads on MSDN forum confirming it.



PluralSight Learning Library