I have a solution that talks to a FoxPro database (dbc) table (dbf) via the MS OleDb provider. Recently we would like to roll this solution out to MS Azure but it says the provider is not installed.
Exception: Unable to find the requested .Net Framework Data Provider.
It may not be installed.
Any idea hot to get this installed? The solution runs on my local machine without errors. I've googled this but unable to find anything specific - however I did see articles that indicated OleDb is not supported yet can be installed.
Here is the direct error message i'm getting on the azure website
The underlying provider failed on Open. The 'VFPOLEDB' provider is not registered on the local machine.
Azure might be running on x64 bit OS. You need to have an Ole DB provider for foxpro that works well for x64 OS. or you can change it to x86 OS
Azure is Microsoft's cloud version of a SQL-Server database, so to connect to that you'll need SQL driver not VFP's OleDB. Now if you need to query one table in VFP and another that is in Azure, I do not believe you can ... even if both are 32-bit, and VFP will only ever be 32-bit anyhow. If you do need to query between both, it would have to be done in a 3-part process I guess. Query from Azure to .Net (like a DataTable result), query from VFP (also to DataTable), then you could manually scroll through the rows and get what you need, such as with LINQ.
Related
I want to create a linked server for connecting to excel file and i have used below address for doing that:
https://www.sqlshack.com/query-excel-data-using-sql-server-linked-servers/
After installing (accessdatabaseengine.exe) the provider has not been added to my provider in sql server.
When i wanted to install accessdatabaseengine_x64.exe i got error because office is 32 bit.
My office is 32 bit version and my sql server is 64 bit version. I do not have permit to re-install of my office and my sql server.
Please help how i can solve my problem.
Masoud,
Architecture versions have to match unfortunately so you would need to install 64-bit office to make that adaptor to work.
You could possibly use SSIS to a raw table and process that way but this depends on your workload and frequency of updates required.
I've had a frustrating time attempting to connect to an Oracle DB as a destination via SSIS so I can export some data into it.
I have Oracle ODAC components installed, tnsnames.ora set up properly, TNSNAMES in the NAMES.DIRECTORY_PATH attribute in sqlnet.ora, Attunity installed on my computer etc. I have even managed to connect to the database in question in the SSIS server explorer, and am able to access all its tables etc.
However I can't seem to find out how to actually connect to that Oracle DB as a destination in an SSIS Project. I started a new package, switched to data flow, selected 'OLE DB Destination' and attempted to create a new connection with either 'Oracle Provider for OLE DB' or 'Microsoft OLE DB Provider for Oracle'. Both only let me cite the server name and user name + password, and when I enter the same ones I used to establish the SSIS server explorer connection I get an 'ORA-12154: TNS: could not resolve the connect identifier specified' error.
I have spent a lot of time trying to fix this but keep running into a brick wall. Any idea what I'm doing wrong or what I could do to establish a connection?
Are you using 32 or 64 bit Windows? I've struggled with some Oracle connections in the past and I made the mistake with mixing up 32 and 64 bit Oracle drivers and settings. Visual Studio is 32 bit and uses those drivers by default, you can go to project properties and change the VS to use 64 bit runtime if necessary.
This could be helpful also: https://stackoverflow.com/a/18098573/5605866
I am new to SQL Server and trying to familiarize myself with it, so I have some questions.
My background is Oracle and am wondering if it works very similar to SQL Server.
On a client machine we need to install a client version of Oracle, and with the installation it comes with a TNSNames.ORA file which has settings for all of the Oracle DB's which are located on an Oracle DB server.
I would assume that SQL server would follow something similar, install a client version of SQL server? If so, does SQL Server has something similar to local Oracle?
I've found how connect to SQL server from another computer, just wondering if I still would need a slim down/client version of SQL Server, I would assume yes.
https://technet.microsoft.com/en-us/library/ms345343(v=sql.110).aspx
Some of you might be asking, why don't you try it, don't have my second computer yet, would like this info. ahead of time.
Thank you
SQL Server client APIs include the low-level components needed to connect to and use SQL Server so there is generally no need to install other connectivity components. To name a few Microsoft ones:
ODBC: Latest version is ODBC Driver 13.1 for SQL Server
OLE DB: Latest is SQL Server 2012 Native Client
.Net Provider for SQL Server (SqlClient): included .NET framework
JDBC: Latest Microsoft version is 6.2
There are also a number of other open source and commercial APIs available for use in various programming languages and development frameworks (e.g. Tedious for Node.js).
I compiled a Powerbuilder 10.2 Program and released it to my users. it uses OLE DB Connection. Its working in any Programmer PCs except for our users. I think i might be missing a DLL or something to release in the Set. The problem is I dont know what I am missing.
Any help?
My throws sent this: MS OLE DB is not provided in the current installation
I think that you need the Microsoft SQL Server Native Client that should be deployed on each user host.
Which version of SQL Server are you using ?
For SQL Server 2005, you can find it in the Feature Pack for Microsoft SQL Server 2005 (look for sqlncli).
I have a web server (Coldfusion) and 2 remote networks that have SQL servers. For both remote offices/networks I query for data every 10 minutes. It has been working for some time now. In one of the offices/networks, AT&T dumped our public static IP address. They assigned a new one and I have made the appropriate changes to the firewall. Now I can use the Windows ODBC manager and test the connection from the web server and it passes just fine. But, when I try to verify the Coldfusion data source, it fails, "timed out trying to establish connection".
ColdFusion 9 doesn't use the Windows ODBC drivers; it uses JDBC drivers. Changing the Windows ODBC drivers and testing them will have no affect on your CF sites.
Update your DSNs in ColdFusion Administrator. Remember, you access your CFAdmin via:
http://localhost/CFIDE/Administrator
unless you've specifically changed it during install. Obviously, replace "localhost" with the server's IP or hostname if it is externally hosted.
ADDENDUM
The exception to the above rule is when you are using the ODBC-JDBC Bridge (CF DSN type = "ODBC Socket"), in which case, you need to verify that:
a) The Windows ODBC Driver (System) is set up, tested, and working, and
b) The CF DSN is pointing to the correct Windows ODBC Driver.
If you are using Windows Server 2008 64-bit, then you may be having trouble with your ODBC because you could be looking at the 64-bit connection list, rather than the 32-bit. In this case, you will have to open up c:\windows\syswow64\odbcinst.exe to access the 32-bit ODBC manager (yes, you read that right; the 32-bit version is under a folder named syswow64).
It sounds to me like there is a good chance that the driver settings you need to update are there, instead of those found registered under the 64-bit ODBC manager (which is the default ODBC manager under control panel). You may have actually had duplicate ODBC entries, one under the 64-bit list and one under the 32-bit list, and this could be the source of the confusion - CF could be using the 32-bit version. In any case - this would be a good thing to check.