Sql Server x64 and x86 Linked Server -

I have a Visual FoxPro table that I need to access from SQL Server In SQL Server x86, I only have one linked server Unfortunately, there is no x64 driver for VFP - then SQL Server x64 can not create a linked server for it.

So far, I have come up with the following options - none of which I am specifically

1. An x86 Sql server to use as a relay Set up so that the question should be from x64-> x86-> VFP.

I really do not care for it, as an addition to Dev, I am also sysadmin, so that means I have to patches another SQL server, maintain and Need to monitor - and possibly another server (assuming I just do not use a different example)

In addition, since VFP providers have not been working with 4 part syntax, I have to use OPENQUERY to avoid all single bids, think that an open statement is open to another Details need to be embedded, spin my head ....

2. Create the CLR table value function, although the assembly (possibly?) Will also be x64 - so I actually run the query Will go out of proc (IPC websites?)

ensures that TVFs require schema, so this option is not as clean as I previously thought. I did a spike to get a WCF client in MSSQL, which gives a single column to XML, which can then be parsed with SQL XML Datatype functions. It works, and in fact it is good to query something compared to OPENQUERY because it actually takes the variable in the form of parameters, it protects me from the same quote and Exec dance.

Of course, the WCF is completely unsupported inside SQL, and smells like a huge hack. I have very serious relationships on performance and reliability.

3. To query VFP from SQL server, and rewrite a good bit of client code

Obviously, this is the "correct" answer but, the client is a good deal of code that relies on connecting between SQL Server tables and VFP tables. Rewrite this content due to populating a temporary table or joining the client side, it seems that there is not a big burden.

Here's hoping someone can recommend a better option or some similar experience.

This is a dirty problem, I agree.

To import data, SSIS is run in 32-bit mode on a regular basis (perhaps on demand, at a job started by the same SP), there is another option in a SQL Server Basic table If you can stand delays. This will depend on problems with the frequency of data changes and the possibility of a little bit of old data.