Microsoft SQL Server
Microsoft Windows - The ODBC database drivers are usually pre-installed with the Windows operating systems.
Linux and Apple MacOS - This is the link to the Microsoft Docs site that outlines how to install the driver based on your specific Operating System: Installing the Microsoft ODBC Driver for SQL Server on Linux and macOS
RStudio Professional Drivers - RStudio Server Pro, RStudio Connect, or Shiny Server Pro users can download and use RStudio Professional Drivers at no additional charge. These drivers include an ODBC connector for Microsoft SQL Server databases. RStudio delivers standards-based, supported, professional ODBC drivers. Use RStudio Professional Drivers when you run R or Shiny with your production systems. See the RStudio Professional Drivers for more information.
There are several that either connect via ODBC but do not provide support for
DBI, or offer
DBI support but connect via JDBC. The
odbc package, in combination with a driver, satisfies both requirements.
There are six settings needed to make a connection:
- Driver - See the Drivers section for more information
- Server - A network path to the database server
- Database - The name of the database
- UID - The user’s network ID or server local account
- PWD - The account’s password
- Port - Should be set to 1433
con <- DBI::dbConnect(odbc::odbc(), Driver = "[your driver's name]", Server = "[your server's path]", Database = "[your database's name]", UID = rstudioapi::askForPassword("Database user"), PWD = rstudioapi::askForPassword("Database password"), Port = 1433)
MS SQL Express
The following code shows how to connect to a local MS SQL Express instance:
con <- DBI::dbConnect(odbc::odbc(), Driver = "SQL Server", Server = "localhost\\SQLEXPRESS", Database = "master", Trusted_Connection = "True")
This section will be updated as new issues are found, and when fixes are applied in the development version of the dbplyr package. The issue will be fully removed when the fix is part of of the package’s version in CRAN.
- RJDBC support - Even though it is not considered an issue, we have found a workaround. The approach is to point the current JDBC connection to the MS SQL translation inside
sql_translate_env.JDBCConnection <- dbplyr:::`sql_translate_env.Microsoft SQL Server` sql_select.JDBCConnection <- dbplyr:::`sql_select.Microsoft SQL Server`
Please refer to the Issues section in
dplyr to find out the latest regarding bugs and resolutions.