Databases
StackOverflow2013
Postsdbo
POSql Server x64 and x86 Linked Server
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSql Server x64 and x86 Linked Server
    primarykey
    data
    text
    <p>I have a Visual FoxPro table that I need to access from Sql Server. In Sql Server x86, I would just create a linked server. Unfortunately, there is no x64 driver for VFP - so Sql Server x64 can't create a linked server to it.</p> <p>So far, I've come up with following options - none of which I'm particularly fond of:</p> <ol> <li>Set up an x86 Sql Server to be used as a relay, so that queries go from x64 -> x86 -> VFP.</li> </ol> <blockquote> <p>I don't really care for this, as in addition to being dev, I'm also sysadmin. So, this means I need to patch, maintain, and monitor yet another Sql Server - and possibly yet another server (assuming I don't just use a separate instance).</p> <p>Also, since the VFP provider doesn't work with 4 part syntax, I have to use OPENQUERY. Thinking of all the single quote escaping that'd need to happen to have an OPENQUERY statement embedded into another OPENQUERY statement makes my head spin....</p> </blockquote> <ol start="2"> <li>Create a CLR Table Valued Function, though the assembly would (presumably?) also be x64 - so I'd have to go out of proc (IPC? Webservice?) to actually run queries</li> </ol> <blockquote> <p>Turns out that TVFs require a schema, so this option isn't as clean as I initially thought. I did a spike to get a WCF client into MSSQL, which returns a single column of XML that can then be parsed with the Sql XML datatype functions. It works, and is actually a little bit nicer to query than OPENQUERY since it actually takes variables as parameters. That saves me most of the single quote and EXEC dance.</p> <p>Of course, WCF inside Sql is wholly unsupported, and smells like a pretty big hack. I have pretty serious reservations on performance and reliability.</p> </blockquote> <ol start="3"> <li>Stop making queries from Sql Server to VFP, and rewrite a good bit of client code</li> </ol> <blockquote> <p>Obviously, this is the "right" answer. But, there is a good deal of client code that relies on joins between Sql Server tables and VFP tables. Rewriting this stuff to populate a temp table or do client side joins seems like a rather large burden.</p> </blockquote> <p>Here's hoping someone can suggest a better alternative, or some similar experiences.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMark Brackett
    1. USMark Brackett
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSql Server x64 and x86 Linked Server
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSql Server x64 and x86 Linked Server
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSql Server x64 and x86 Linked Server
      1. This table or related slice is empty.
      1. VTDownMod
    1. COWe ran into a similar problem when trying to convert FoxPro data to SQL Server on a 64-bit machine. since this was a one shot deal went with your first option.
      singulars
      1. POSql Server x64 and x86 Linked Server
      1. USClinemi
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload