Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I need to connect to Netezza DB through R studio. I checked some pages already, the answers weren't clear. I don't know much about ODBC drivers and stuffs.
I have this folder that has bunch of dll and .jar files.
C:\Program Files (x86)\IBM Netezza ODBC Driver\jre.
Do i have to download any drivers and are there any specific R packages to install for this.
I did this with RODBC package.
First, make sure ODBC connection is set up in ODBC Data source Administrator(Windows system).
Install RODBC package in R studio.
library(RODBC)
myconn <-odbcConnect("ODBC_connection_name", uid="user", pwd="pass")
q_df <- sqlQuery(myconn,"select * from table", believeNRows=FALSE)
By default only 256 rows is imported. Set believeNRows=FALSE will import all the rows
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 1 year ago.
This post was edited and submitted for review 1 year ago and failed to reopen the post:
Original close reason(s) were not resolved
Improve this question
I received a SAS file (.sas), but I don't have a SAS license, would it be possible to open this file in R using some package in a simple way?
With the .sas file open in R I intend to access the database that is associated with it. I could do this using a temporary SAS license, but for me it will be too bureaucratic to do so, and I am more familiar with R which is 100% free.
NOTE: I can't share the file because it's third-party data.
In RStudio, in the Files pane navigate to the file you'd like to open.
Click on the file and select View File and it will open.
.SAS files are text files that store programs they typically do not create data unless it's a data step that has data.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 4 years ago.
Improve this question
I am trying to connect to Snowflake using odbc connection. I have created a user DSN in odbc data source administrator on windows. When I am trying to connect through odbc in c#, its giving me an error that data source name not found and no default driver specified. Can anyone give me an example of connection string needed for same and how I could fix this error. I am using Visual Studio for development.
Visual Studio IDE is 32-bit.
The original User DSN was set up with a 64-bit ODBC driver for Snowflake.
The solution was to install and set up a DSN with a 32-bit ODBC driver for Snowflake.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 7 years ago.
Improve this question
In relation to Teradata Client 14.10, I was wondering if I could use this tool to run SQL, view tables and change passwords?
New to teradata.
Many Thanks.
Use the SQL Assistant from the client set, it would suffice.
Studio is too cranky at this point, was supposed to be an equivalent eventually replacing the assistant.
... teradata studio; a pre-baked eclipse plugin. Works pretty well and doesn't require all the old men ODBC configuration '90s msft weirdness. sorry a 'lil high rugh now.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I did not try before to include .MDF file in App-Data, I usually connect to Sql Server 2005 or 2008 DB. Why I would use the mdf file, and what is the Pros and Cons.
Thanks
The .mdf file in App_Data is usually associated with SQL Server Compact editions. In production you would prefer to use the full blown version of SQL Server. The local database is good enough for development and testing purposes.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
Has anyone connected the R package to QuickBooks? I know there is an ODBC driver than can be bought. Just wondering if anyone has already gone down this road.
Any insight will be much appreciated!
~ Brock
Google QODBC. It allows you to access Quickbooks via ODBC.
However, it works through creating an interface to XML files. For large QB files it can be painfully slow if you don't properly use indices and limit the data to exactly what is necessary. It's also very quirky. Lastly, not all tables are exposed (Quickbooks fault, not theirs) such as some payroll tables.
What I often ended up doing for large QB files is exporting the data at night via the QODBC driver into a sql database so that ad hoc analysis could be run quickly without compromising the performance for QB users during the day.
Good luck!