64 bit, Importing from dBase or other DBF files

Microsoft in the News

On January 10th, Bob Evans, contributor to Forbes magazine, crowned Satya Nadella the CEO of the year in the area of cloud computing.  In the scant four years that Mr. Nadella has been at the helm, he has transformed Microsoft, and in doing so, more than doubled its market cap.

But most importantly, according to Bob, Mr. Nadella’s impact on cloud computing has been stellar.  While chasing Amazon, and fending off Google, IBM, and Salesforce (all of which have pulled off stellar years of growth), Microsoft is now the one to beat.  In fact, it looks like Microsoft will be the first to reach $20 billion in annual enterprise-cloud revenue (an arbitrary, but meaningful mark).

The full story can be found here:  https://www.forbes.com/sites/bobevans1/2018/01/10/the-tech-industry-ceo-of-the-year-microsofts-satya-nadella/#17e5c306c627


Importing from dBase or other DBF files

In my last blog, I described how to import dBase and DBF files into SQL.  The process needed a good review since the import wizard will not work.  As I pointed out in my last blog, although my solution works, if you are running 64-bit SQL, a different set of issues crop up.

Also in my last blog I had given a link that described the problem.  In that link it was mentioned that you could import the file into Access or Excel, and then import to SQL from there.  To me, that just seems in-elegant and will likely produce another set of problems.  So, like so many geeks who follow my blog, I prefer to solve these problems without resorting to the brute force method.  Here is part 2 of solving the problem of importing dBase or other DBF files, this time addressing the issues pertaining to 64-bit SQL.

If you are running on a 64-bit version of SQL Server you will have to run the entire package in 32-bit mode, not just the connection strings and data access, but the entire SSIS package.  The process to switch to 32-bit mode is as follows:

  1. Choose Project inside VisualStudio
  2. Select YourProject Properties…. From the menu
  3. Expand the Configuration properties so you can see and click on Debugging
  4. Under the debug options, on the right, change the value of the Run64BitRuntime value to False.
  5. Choose OK

Ensure that when scheduling your package to run in the Agent, you choose “Use 32bit runtime” in your Execution options when creating the job.


I hope I have made your life just a little easier

Leave a Reply

Your email address will not be published. Required fields are marked *