similar to: RODBC and sqlSave issue

Dear Tobias, I finally succeeded in exporting my dataframes from R into Access with this script: library(RODBC) canal <- odbcConnectAccess("D:/Floristique.mdb") sqlSave(channel=canal, dat=flore, tablename="Floristique", rownames=F, safer=F, fast=F, varTypes=c(dates="Date")) odbcClose(canal) My problem in exporting my dataframe "flore" seems to

Hello, After a (bad) first try some months ago, I'm trying again to use RODBC package instead of DBI+RMySQL packages to populate MySQL database. The main command is sqlSave(channel, data_df, tablename, append=T, rownames=FALSE, colnames=FALSE, fast=FALSE, varTypes=vartypes) where data_df is the data.frame I want to save and vartypes is obtained following the tip given here

Till yesterday I was more than satisfied by RODBC, specifically by sqlSave which I had been happily using in a daily crontab R batch job regularly updating a postgresql db for as long as one year. In this R- batch I was able to save records into indexed tables *** even though *** they already existed. in this case sqlSave simply neglected those rows of the input table that were offending the

Hola Javier, si no estoy entendiendo mal, lo q deseo hacer no se trata de configurar los parametros SQL, sino solo de colocar un vector en el argumento VarTypes de la funcion sqlSave. El manual especifica esa opcion, pero no da ningun ejemplo de como usarla. *varTypes an optional named character vector giving the DBMSs datatypes to be used for* *some (or all) of the columns if a table is to be

Buen dia Javier, muchas gracias por tu ayuda y el script compartido. Me va a servir como ayuda para seguir aprendiendo sobre RODBC pero no encuentro una solucion para este problema puntual de poder definir el tipo y ancho de las variables, q segun creo se hace con el argumento varTypes. Si alguien tien algun ejemplo donde haya usado la SqlSave y VarTypes, me sera de gran ayuda. Abrazo a todos

I am running R version 2.8.1 on Windows XP OS. This works fine. (Data.frame dta is created with records from the DB2 table.): sql <- "select * from storage.testappend_slt order by uut" dta <- sqlQuery(channel,sql) But when I try to append records (from data.frame newdta) to the same DB2 table. I get an error: sqlSave(channel, newdta, tablename = storage.testappend_slt, append

I am using R2.6.0 on “Windows Small Business Server 2003”. I apologize if the answer to my question is available…I have searched but have not found anything that I thought helped me. I have a dataframe that contains ~4.5 million rows and 5 columns. (see memory and df details below). I am trying to save the dataframe to a MS SQL Server database, using the “sqlSave” function. The code

Buen dia compañerxs de R, les traigo una pregunta bastante especifica. En el trabajo me estan requiriendo el uso de SQL, asi q estoy aprendiendo a usarlo desde R, con el paquete RODBC. Mi problema puntual es que al crear una tabla en el servidor SQL a partir de un data frame en R (usando la funcion sqlSave) no puedo definir el tipo de variables que quiero usar en el data frame. Segun entiendo

Hi, I am trying to use sqlSave to write a dataframe to an existing table in a DB2 database. The database contains two schemas. My experience is the following: (1) in the case that tablename is left empty in sqlSave, R writes to the instance level schema (2) in the case that a tablename is specified and that table name exists only once in the database, R will write to that table irrespective

I have an existing table, and I am trying to use sqlSave to append additional rows to this database. I omit the primary key, which is a uniqueidentifier type (MS SQL), so that the database can populate that field. However, I get the following error: > sqlSave( ch, result, tablename=thetablename, append=TRUE, rownames=FALSE, colnames=FALSE ) Error in odbcUpdate(channel, query, mydata,

Hey everyone, I don't have a question. Instead some helpful advice with things I've learned from trying to connect 'R' to databases using RODBC. ROBDC is a very handy tool that, once you have everything fixed up nicely, is a great way to have scripts run fairly autonomously, safe in the knowledge that data isn't accidentally messed up. But I was fairly ignorant

Good day, all. I just upgraded to R 2.6.0. I re-installed my most-used packages including RODBC to be sure I'm up-to-date. I have been working with a large insurance claims dataset stored in a MS-Access database on a Windows machine. I have been regularly exporting tables from R into it using sqlSave. It's worked like a charm until today, when this happened: >

Hi Everyone, I'm so confused. I've been trying to save data to a table but I keep getting an error that says the table does not exist and at other times saying that it does. So here are some statements: > sqlQuery(channel, "select top 1 * from > TestDB.[SILICON\\holouis1].clep_tier_shift") State NB Change_Number 1 IL 2005-02-08 7 It exists and I

Hi all, I'm using RODBC library to connect to a database. I'm trying to read a table from a database and after manipulating it would like to write to the same database but with a different table P<-data.frame(sqlQuery(myconn,'select? *? from Demographics')) sqlSave(myconn,p,tablename="trial",rownames=FALSE) I'm gettng this error Version:1.0

Hi, I am having trouble to write/create a table, which has a date field. I want to create a stock price table, which has fields of ticker, date, price. First, I created such a table in Microsoft Access with a few rows inputs. Using sqlQuery, I found that the date field was retrieved as POSIXct value. Then I made a data.frame with POSIXct as the data type for dates. However, I received the

Do not use R-bugs for reports on compatibility of obselete versiond of packages with unreleased versions of R! You did not give the RODBC version no. The current version, 1.1-3, is compatible with R-devel. 1.1-2 was not (alongside a dozen or so CRAN packages). The only bugs here are in the report. On Thu, 24 Feb 2005 david.whiting@ncl.ac.uk wrote: > Full_Name: David Whiting >

Hello, I'm still trying to modify my script in order to use RODBC instead of RMySQL (no more ready-to-use package for windows). My new problem is the following one (not seen with RMySQL): I'd like to copy a data.frame to a mysql table. One column is a numeric one with big integer like : 2005000206110 (13 figures) If I type this number in R, I get: 2.005e+12 and when I use sqlSave to

Dear R users, I've already asked this question yesterday, but, though I had answer for the other ones (and they helped a lot, thanks), for some reason didn't get an answer for this one (I would also appreciate to know why, so that I can improve the quality and clarity of my future questions). Here it is again: I'm trying to use RODBC to export dataframes to xls files. When I run

All, I am new in R. I found sqlSave() doesn't work for our Oracle9i. The following was the message: > sqlSave(channel, USArrests, rownames="state") Error in sqlColumns(channel, tablename) : USArrests : table not found on channel Check case parameter in odbcConnect > sqlQuery() works OK. Please help. Thanks. -MY

Dear R users, I have a follow-up question on sqlSave(). Since most of the output from the tests I use are lists, I would like to loop to export each element of the list and append it to the sheet. Here is what I do: > library(RODBC) > test <- structure(list(m = structure(c(0.090909090909091, 0.181818181818182, 0.272727272727273, 0.363636363636364, 0.454545454545455,