Analyze Sage 200 Data in R via JDBC

Access Sage 200 data with pure R script and standard SQL on any machine where R and Java can be installed. You can use the CData JDBC Driver for Sage 200 and the RJDBC package to work with remote Sage 200 data in R. By using the CData Driver, you are leveraging a driver written for industry-proven standards to access your data in the popular, open-source R language. This article shows how to use the driver to execute SQL queries to Sage 200 and visualize Sage 200 data by calling standard R functions.

Install R

You can match the driver's performance gains from multi-threading and managed code by running the multithreaded Microsoft R Open or by running open R linked with the BLAS/LAPACK libraries. This article uses Microsoft R Open 3.2.3, which is preconfigured to install packages from the Jan. 1, 2016 snapshot of the CRAN repository. This snapshot ensures reproducibility.

Load the RJDBC Package

To use the driver, download the RJDBC package. After installing the RJDBC package, the following line loads the package:

library(RJDBC)

Connect to Sage 200 as a JDBC Data Source

You will need the following information to connect to Sage 200 as a JDBC data source:

• Driver Class: Set this to cdata.jdbc.sage200.Sage200Driver
• Classpath: Set this to the location of the driver JAR. By default this is the lib subfolder of the installation folder.

The DBI functions, such as dbConnect and dbSendQuery, provide a unified interface for writing data access code in R. Use the following line to initialize a DBI driver that can make JDBC requests to the CData JDBC Driver for Sage 200:

driver <- JDBC(driverClass = "cdata.jdbc.sage200.Sage200Driver", classPath = "MyInstallationDir\lib\cdata.jdbc.sage200.jar", identifier.quote = "'") 

You can now use DBI functions to connect to Sage 200 and execute SQL queries. Initialize the JDBC connection with the dbConnect function.

• Schema: Determines which Sage 200 edition you are connecting to. Specify either StandardUK or ProfessionalUK.
• Subscription Key: Provides access to the APIs that are used to establish a connection. You will first need to log into the Sage 200 API website and subscribe to the API edition that matches your account. You can do so here: https://developer.columbus.sage.com/docs/services/api/uk. Afterwards, the subscription key may be found in your profile after logging into Sage 200.

Built-in Connection String Designer

For assistance in constructing the JDBC URL, use the connection string designer built into the Sage 200 JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

java -jar cdata.jdbc.sage200.jar

Fill in the connection properties and copy the connection string to the clipboard.

Below is a sample dbConnect call, including a typical JDBC connection string:

conn <- dbConnect(driver,"jdbc:sage200:SubscriptionKey=12345;Schema=StandardUK;InitiateOAuth=GETANDREFRESH;")

Schema Discovery

The driver models Sage 200 APIs as relational tables, views, and stored procedures. Use the following line to retrieve the list of tables:

dbListTables(conn)

Execute SQL Queries

You can use the dbGetQuery function to execute any SQL query supported by the Sage 200 API:

banks <- dbGetQuery(conn,"SELECT Id, Code FROM Banks WHERE Code = '12345'")

You can view the results in a data viewer window with the following command:

View(banks)

Plot Sage 200 Data

You can now analyze Sage 200 data with any of the data visualization packages available in the CRAN repository. You can create simple bar plots with the built-in bar plot function:

par(las=2,ps=10,mar=c(5,15,4,2))
barplot(banks$Code, main="Sage 200 Banks", names.arg = banks$Id, horiz=TRUE)