I'm attempting connect my Sequel Pro database to R. In Joseph Adler's "R in a Nutshell"- page 164- he lists various ODBC drivers for different databases, but I can't find one for Sequel Pro. Any help on which driver to use would be greatly appreciated.
I don't have a Sequel Pro database, but here are the steps you would likely follow:
Install the proper ODBC driver (http://dev.mysql.com/downloads/connector/odbc/)
Add the database as an ODBC DSN. This is available in Windows in Administrative Tools -> Data Sources (ODBC). (Enable by right-clicking on Start Menu, "Customize...", and select one of the display options under "System administrative tools".) Add the database under "File DSN" (most likely) or "User DSN".
Use R to open ODBC connection:
library(RODBC)
dsn <- "this is the dsn assigned in the windows tool"
db <- odbcConnect(dsn)
sqlQuery(db, "select * from whatever")
sqlSave(db, df)
Data in df. Sorry I can't give you the exact process, but I don't have the necessary data.
Related
I am unable to connect to a kdb+ database in Power BI via the qodbc3 ODBC driver. After selecting Get Data -> Other -> ODBC and selecting a qodbc driver connection that I know works (used without issue by Tableau) I get stuck at the navigator window and there is no option to load a table.
My concern is that kdb driver is not compatible with Power BI which is causing Power BI to not be able to find database tables.
Although this option was not available back when the question was asked, today's solution to this problem would be to use the Simba ODBC Driver:
https://code.kx.com/q/interfaces/odbc-simba/
The primary target for this release is support for:
Tableau (certification compliance included)
PowerBI
Excel
I created a data flow task in SSIS. On double clicking, that task I added up ado.net source and destination. Under ado.net destination, I selected connection manager as odbc, and selected a user dsn.
Now, before doing all this stuff, I installed odbc driver from ch-werner.de and created a user dsn. In that process, I selected sqlite3 driver and my database is with the extension .sqlite.
Now, that dsn is available at ado.net destination. But when I select table it shows me this error that "The specified DSN contains an architecture mismatch".
To fix this stuff up, I researched some of the links. One was like, creating a 32-Bit data source names by running c:\windows\sysWOW64\odbcad32.exe. But, when I am trying to create a new dsn through that, it's not having SQLITE3 driver under create new datasource.
I uninstalled sqlodbc. Restarted my pc and ran the sqlodbc installation again. Then, I was able to see sqlite3 drivers by running c:\windows\sysWOW64\odbcad32.exe
I want to connect to HP Vertica from Tableau so that I can visualize directly from Tableau.
Can t find the ODBC driver for Vertica database 6.1
Says coming soon but nothing on the downloads tab since November 2014
MAC:
I found the 6.1 driver at https://vertica.hpwsportal.com/catalog.html#/Product/%7B%22productId%22%3A%22762%22%7D/Show
--- list of recommended drivers for Vertica versions can be found at http://kb.tableausoftware.com/articles/knowledgebase/drivers-vertica
I put the driver in the location /Library/ODBC/
Download TableauDrivers.dmg from http://www.tableausoftware.com/support/drivers
DONOT forget to rename the folder vertica-odbc-6.1.3-0.64.mac to vertica
Use the Tableau Vertica Configure.pkg to configure
Restart
Add server connection details in tableau
Viola!
I'm trying to find out how to connect to a FileMaker Pro 9 Database file (*.fp7) with ODBC. I followed the manual and installed the ODBC driver which now shows up as "DataDirect 32bit SequeLink 5.5".
However I can't find any instructions on how to connect to the Database File. I want to use LibreOffice Base (and maybe later on create my own app) to access Filemaker tables.
Any help would be appreciated! (Please note that I'm new to Filemaker as well as to ODBC)
You need the ActualTech software to connect to the database: http://www.actualtech.com/scenario_ess_setup.php
I don't know if it is down compatible with FileMaker 9 but you might want to upgrade to FileMaker 13 at this point.
They guys at ActualTech are also very helpful.
Once you installed it, you can set up a DSN in the ODBC manager.
I have an Access 97 database that serves as a front-end, via ODBC and linked tables, to a MySQL database, running under Wiin7-64. (Yes, it does work!) The database contains info about places of worship and pilgrimage in the part of France where I live. In addition, I have tens of thousands of photos of the sites in Photoshop Elements 9. The underlying database engine of PSE9 is SQLite, and interesting data about the photos is there (titles, which ones I like, etc.). I would like to link from Access to the tables in the SQLite database as I do to the MySQL database.
My problem: I am unable to create an ODBC connection to the PSE9 SQLite database. I have done multiple searches via Google, read multiple posts at stackoverflow and elsewhere, tried various suggestions, and still no ODBC connection, neither in the 32bit or 64bit ODBC tools of Win7-64. I'm stumped.
So far, I've
downloaded sqliteodbc.exe from http://www.ch-werner.de/sqliteodbc/ and run it (multiple times)
copied sqlite3odbc.dll, sqlite3.def, sqlite3.dll, and sqlite3.exe to the \windows\system32 folder
entered this command at the Windows command line: "rundll32 c:\windows\system32\sqlite3odbc.dll,install", which produced this error message "Copy c:\windows\system32\sqlite3odbc.dll to c:\windows\system32\sqlite3odbc.dll failed."
When I look at the ODBC and ODBC (32-bit) windows, I don't find a User DSN, System DSN or File DSN for SQLite. Any suggestions?
Thanks,
Harvey in balmy Bordeaux
Whats with all that copying dlls around - you don't need to do any of that. Just download the 32 bit version and double click on it - the driver will be installed. Then find the 32 bit ODBC Administrator (note there are 2 on 64 bit windows and only one is 32 bit), fire it up and create a DSN. You should see sqlite3 in the drivers tab.
DSNs are not there automatically, you have to create them yourself. There should be an "Add" button in the ODBC administrator. Then you select the type of driver "SQLite", and then configure the details in the next dialog.
A DSN normally contains all the configuration information needed to connect to a specific database instance so that all this - which may be different from one database system to the other - can be referenced by one name. That is where the name "Data Source Name" comes from.