similar to: RODBC : how to avoid truncatig big integer when using sqlsave

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

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

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

Hello, I'm trying to modify my r-script to use RODBC instead of DBI/RMySQL (no more ready-to-use package for windows). I would like to copy a data.frame of 44 columns to a table of 45 columns (the 45th is an autoincremental column). With the following commands, colnames(df)<- a vector with the names of the 44 columns

Hello, I contact you after having unsuccessfully asked my question to R mailing list. I use the package RODBC to connect to a MS-SQL server. I am able to getQuery from the database. I am now studying the sqlSave some data into the database. Unfortunetly, I meet some issues relating to the format of the data that arrives into the database. I have three columns. The first one should be in the

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

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

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

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

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

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 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,

Full_Name: Paul MacManus Version: 2.3.0 OS: Windows XP Submission from: (NULL) (216.90.169.253) See also R-help thread for October 18, 2006 --------------------------- Create a dataframe and save it to a database table "test" as follows: df <- data.frame(T=1, S=10) sqlSave(channel, df, "test", rownames=F) The table now looks like T S 1 10 If I create another

I am using sqlSave to save my data into an existing table at MS SQL Server database. Previously my code ran smoothly but all of a sudden it stopped working. Here is my code: sqlSave(con, highVol, "dbo.futuresHighVol", append=TRUE, rownames=FALSE) Error: sqlSave(con, highVol, "jrgchis.dbo.futuresHighVol", append = TRUE, : 42S01 2714 [Microsoft][ODBC SQL Server Driver][SQL

Hi, Using the fast=F option, sqlSave saves without matching column names. It looks like a bug to me.......... Here's a simple (artificial) example. ----------------------------------------- Create a dataframe and save it to a database table "test" as follows: df <- data.frame(T=1, S=10) sqlSave(channel, df, "test", rownames=F) The table now looks like T S 1 10 If

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, i get error after using a data.frame with subset for "sqlSave". What can i do ? It seems that lines like this in a data.frame structure are after subset deleted and cause the error ? - attr(*, "variable.labels")= Named chr "CUSID" "Welle" "Arbeitgeberfavorit1" "Aktuelle Bewerbungssituation" ... ..- attr(*, "names")=

Hi all: I have created a MS Access table named 'PredictedValues' through the statement below: myDB <- odbcConnectAccess("C:/Documents and Settings/Owner/Desktop/Rpond Farming.mdb",uid="admin",pwd="") sqlSave(myDB,PredictedValues,rownames=FALSE) close(myDB) But if I run the code again with new values I get the message below: Error in sqlSave(myDB,

Dear list, Being new to both the postgres database, ODBC and the RODBC interface, I am somewhat confused by some of the problems I am experiencing trying to connect R to the database. Whai I am trying is basically the example part of the help file for the sqlSave function: > library(RODBC) > odbcConnect("theodor") -> channel > data(USArrests) > sqlSave(channel,

Dear R-community, After repeating the sqlSave-command 3 times on a dataframe (of size 13149 rows * 5 columns) to my MS-Access database I get the following error: *Error in sqlSave(channel, eksport_transp_acc_2, "transp_acc_scenarier", : unable to append to table ‘transp_acc_scenarier’* ** This means that the first 2 savings are completed, but the third-one is somehow not. I have an