RJDBC | R interface to databases using JDBC | DB Client library

As it turns out, there was a bug in the previous version of the driver and updating the driver to latest version fixes the issue.

This one is a related issue here https://github.com/snowflakedb/snowflake-jdbc/pull/434 and you can install the latest version of the driver from here https://repo1.maven.org/maven2/net/snowflake/snowflake-jdbc/

Note that the version number is not sorted numerically on that page.

I do this using dbExecute from the DBI package.

The key idea is to extract the query that defines the current remote table and make this a sub-query in a larger SQL query that writes the table. This requires that (1) the schema exists, (2) you have permission to write new tables, and (3) you know the correct SQL syntax.

Doing this directly might look like:

RJDBC pre-dates the more recent DBI specification and uses a different function to access this functionality: RJDBC::dbSendUpdate(con, query) .

DBI's dbSendStatement() doesn't work here yet. For best compatibility, RJDBC could implement this method and forward it to its dbSendUpdate() .

The problem is that you have Java 8 installed on your machine, but Driver was build for java 14 (class file version 58.0 tells that).

You can either install java 14 on your machine or get a JDBC driver for Java 8.

A link for SQL Server JDBC driver for java 8

In your attempt without DSN the parameter ServerNode is missing; you used HOST instead, which is not the same parameter.

See the reference documentation here for details.

First, always reference column by name in aes and not by [ or $ of the same data frame. Second, you need to clean up your columns, ELEMENT_LABEL and plot_order, before plotting.

• Run droplevels as ELEMENT_LABEL currently has 54 levels for only 28 observations! Likely, your plotting data frame derives from a filtered version of original. After doing so, you reduce to 8 levels across 28 observations.
• Re-assign values of plot_order column by the unique values, not simply an integer sequence across length of rows. Specifically, plot_order must order the 8 unique values to correspond to each unique occurrence of ELEMENT_LABEL. You can achieve this with inline aggregation like ave calling min to take lowest number for same ELEMENT_LABEL.

Once you clean up these two columns, plotting then should adjust:

Capture the static parts of your query in an object

To successfully run an ALTER SYSTEM command, you don't need to be the DBA, but you do need the ALTER SYSTEM privilege to be granted to you (or to the "user" owning the application through which you connect to the database - which may be different from "you" as the "user" of RStudio).

You have a few options:

• ask the DBA to kill the session
• ask to be granted the ALTER SYSTEM privilege (which is a very poor practice)
• have a "supervisor" (however defined - responsible specifically for these situations) be granted the ALTER SYSTEM privilege, who will be in charge of killing such sessions
• (perhaps the best option) create a packaged procedure whose only task is to kill orphaned sessions. Grant ALTER SYSTEM to the package owner, and grant execute privilege on that package to individual users (as needed). The procedure should be written to only kill specific kinds of sessions.