Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve seen many solutions on how to convert DBF files into a SQL database, but is there anyway to convert the tables without re-coding the program that refers to the DBF files?
For example convert the DBF files into SQL tables, then leaving the dbf files in place with only a pointer to the SQL database?
The goal would be to allow the existing application to run (until we migrate the code) but keep the data in SQL?
I don’t think you’re going to find a tool that will link to SQL from within a DBF context and allow your code to flow seamlessly through the DBF to your SQL Server keeping both current along the way.
Depending on how complex or extensive your daily transactions are I would recommend setting up some SSIS packages that run on a regular basis to keep the data from your DBF files flowing to your SQL tables until you are ready to commit to SQL full time.
Another option might be to approach it going the other direction. Set up a linked server or open rowset from within SQL to your DBF files and then build some stored procs on the SQL end that merge the data on a regular basis using tsql merge statements or other queries that you’d have to build.