Convert dbf database to SQL server database mdf

Convert Foxpro dbf database to SQL server database mdf/oracle/dbase


Yes, there's a way

http://www.foxdev.com/VFPonSQLSGeneric.pdf
http://www.spectralcore.com/fullconvert/tutorials/convert-dbf-dbase-foxpro-to-mssql-sql-server.php

but before converting ask your self first. Why do you need to convert?

Know the difference first

DBFs are accessed from a file server- since most servers itself can act as a file server,there's no need for you to buy another database server. BUT if you need more security and your company possess a LOT of database then it's time for you to buy a database server (eg. Microsoft SQL Server 2008)

dbf variations =FoxPro (now Visual FoxPro), Arago, Force, dbFast, dbXL, Quicksilver, Clipper, Xbase++, FlagShip, Recital, CodeBase, MultiBase and Harbour/xHarbour

ADVANTAGE of dbf than SQL SERVER
+fastest data system available on the PC platform. Even greater than any SQL Server outthere.
+Simplicity-easy copying or moving of the entire application database simply by copying the a VFP DBF application directory to any other location (but the again SQL can also backup database automatically)
+Programming-alot of people out there knows how to program this since it uses traditional SQL techniques -(but for me hmmm it still depends... there are other PL out there)

DISADVANTAGE of DBF THAT I experience with FoxPro dbf

Safety
-data files can become corrupt due to network or workstation interruptions.
-since typically all program users have full rights to the directory containing the data, an individual could (accidentally or maliciously) delete or overwrite one or more data files, or modify a data file from outside the VFP application, potentially introducing errors or corruption
-you can restrict accidental of file BUT there is still a way to acces it

Data Integrity
-While later versions of VFP have added the ability to enforce some forms of data integrity at the datafile level, these enhancements do not have the performance or robustness of those found in SQLS.

Technical Limitations
-DBF files are limited by Microsoft to 2 gigabytes in size for each DBF


SQLS data is accessed from a database server - Thus you need to buy another software BUT then again it offers more security and functionality.
-Microsoft SQL 2008, Dbase, Oracle
-provides for interfaces for getting things in and out without direct access to the underlying storage files.

ADVANTAGE of SQL:
+SQLS inherently uses multiple processors
+can be clustered onto multiple server machines
+Data Intergrity-if the server is told never to
allow deletes of a client if there are orders existing for that client, then it is an impossibility (absentdatabase administrator override) for that to happen,even outside of a VFP DBF application (since it is stored in the SQL Server as one file... so the user can't just delete the databse it self) unlike with dbf If I can access the network I can get the ownership of that dbf and delete it.
+Data Security-Users would not be able to copy or delete data files, even those who otherwise have access to the data through a VFP DBF application
+Data Access-SQLS provides a number of ways for users to access its data via ODBC. Users could access via a FoxPro application; via MS Access or Excel (if allowed), or remotely from outside the organization. (unlike with dbf you are usually stucked with Visual FoxPro well unless you converted the dbf)
+SQLS provides for optional replication, which allows data changes on one server to automatically migrate to another server.
+Finally, since the vast majority of the filtering is done at the server rather than the workstation, the network speed and client workstation power are less-important.
+Progamming-There are lots of PL langauge you can use to access mdf (sql) database. As long as you know how to use ODBC then you are fine. (hmm dbf can also be accessed with odbc but then again...SQL Server in the end has much more thigns to offer)
+And ohhh you can access dbf also through Microsoft SQL Server 2008 also

DISADVANTAGE of SQL SERVER
-Complexity - Database servers require more maintenance and
tuning than a file server.

note:The application could support a mixed-scheme approach, where some data could be in DBFs and other data in SQLS.

-Cost. Yes Microsoft SQL Server cost much but there are free versions called Express (but then again there are limitations with free)


Summary
The single-greatest hindrance to moving to SQL Server as VFP application data storage system is the time and expense of rewriting parts of a VFP DBF application to support SQLS. This work could be done incrementally, one table/data file at a time.
However, the potential benefits of moving a VFP DBF application to SQL Server are clear, particularly in regards to much more flexible data access and much stronger data integrity.

(Agree the time spent in rewriting, but for the new apps you will build maybe Its time to move to SQL servers...remember Security now is an issue! especially in bank company)



for comparison read this article


Thanks -www.foxdev.com