The R import/export manual discusses various approaches to handling data and mentions that R is not suitable for working with large data sets because data objects are stored in memory during a session. There are situations where using a database to hold the data and making use of one of the R libraries for database connectivity to access the data or to save the data.
MySQL is a popular database system and there is a library RMySQL that can be used to access this database – it is important to ensure that the version of MySQL matches with the R library. If there isn’t a match then the system might exhibit erratic behaviour.
The first step is to make the RMySQL library available in the working session:
If this command runs without problems then we need to create a connection object for our session:
con = dbConnect(MySQL(), dbname = "test", user = "user1", password = "pwd1")
The first argument to this function creates and initializes a MySQL client. It returns an driver object that allows you to connect to one or several MySQL servers. The dbname argument is used to specify the name of the database and the user and password arguments should be self-explanatory.
After creating our connection successfully we can get R to list the tables that are stored in this database:
> dbListTables(con)  "co2"
In this example there is only one table and its name is returned by the dbListTables function. To read the data from this table we use the dbReadTable function and specify the connection object as well as the name of the table in the MySQL database:
> dbReadTable(con, "co2") Plant Type Treatment conc uptake 1 Qn1 Quebec nonchilled 95 16.0 2 Qn1 Quebec nonchilled 175 30.4 3 Qn1 Quebec nonchilled 250 34.8 ...
We can save the table to a data frame object rather than the default action of printing to the console.
After undertaken some analysis we might want to save a data set to the database and the dbWriteTable function is used:
> dbWriteTable(con, "CO2", data.frame(CO2), overwrite = TRUE)  TRUE
The first argument is the connection object, the second is the name that the table will be referred to in the database and the third argument is the data to be saved. In this case we have used the overwrite argument to copy over any existing table of the same name.
We can delete a table using the dbRemoveTable function:
> dbRemoveTable(con, "CO2")  TRUE
and when we reach the end of our need for the connection, the dbDisconnect function will remove the connection that we have been using:
> dbDisconnect(con)  TRUE