Salesforce ODBC driver
What's new?
Version 2.1 of the Salesforce ODBC driver now supports Salesforce instances that have been integrated with the following single sign-on (SSO) mechanisms:
- Azure Active Directory (AD) Single Sign On (SSO)
- Active Directory Federation Services (ADFS) Single Sign On (SSO)
- OneLogin Single Sign On (SSO)
- Okta Single Sign On (SSO)
Version 2.1 (or later) is also the recommended Salesforce ODBC driver build for Windows 11 and Windows Server 2022.
TDS Server Use Transact-SQL (T-SQL) statements to work with Salesforce data in SQL Server
Version 2.0 of the Salesforce ODBC driver now includes two drivers: one that supports SQL and one that supports SOQL, Salesforce's native query language.
The Windows Salesforce ODBC driver now supports OAuth.
Which driver should i use?
Both drivers enable you to connect 64-bit and 32-bit applications such as SQL Server, Microsoft Office, Oracle, OpenOffice, SAS, and SAP to Salesforce. They provide real-time access, no data extraction is required. Both drivers are kept up-to-date with Salesforce's recommended Transport Layer Security (TLS) version and this will always be the case.
The SOQL-based driver:
- Enables you to leverage existing SOQL knowledge and extends the number of applications that you can use SOQL from.
- Has a lightweight architecture, and is our fastest Salesforce solution, delivering your Salesforce data quicker and reducing Salesforce API consumption.
- Is the most efficient way to join Salesforce tables.
- Supports bulk operations. You can commit multiple
INSERT
s,UPDATEs
, orDELETE
s in one batch, again, greatly reducing Salesforce API usage (which is subject to daily limits).
The SQL-based driver, which prior to version 2.0, was our sole Salesforce offering:
- Enables you to leverage existing SQL experience and resources. For example, you may have a number of T-SQL or Oracle SQL scripts, which the SQL-based driver will let you reuse for Salesforce.
- Lets you take advantage of SQL extensions not available in SOQL. For example, SQL functions.
- Caches Salesforce data locally and lets you alter the preferred batch size for queries, which alters the number of Salesforce API calls it makes. Both mechanisms are transparent to the application and help offset the inevitable overhead associated with translating from SQL to SOQL.
- Supports applications which don't allow you to execute passthrough SQL.
- Enables you to join Salesforce tables that don't have a relationship defined for them in Salesforce. For example, if a there is no built-in relationship for tables you want to join, you could use the SQL-based driver to create a join without the additional step of defining the Salesforce relationship yourself.
In situations where there is no clear-cut case to use one driver or the other, we recommend that you try both drivers and decide which is best for you based on your own criteria.
Our dual driver approach means you have clarity about how the driver works with Salesforce data. The SQL-based driver converts SQL to SOQL. The SOQL-based driver passes SOQL straight through to Salesforce. You, not the driver, control which method is used.
Existing customers can upgrade to version 2.1 and try a parallel or replacement SOQL-based approach. If you are a supported customer, this is a free upgrade, so you have nothing to lose by evaluating the new driver.
For information about how to use the SQL- or SOQL- based driver with a number of popular applications, refer to the tutorials section.
Overview
With the Salesforce ODBC driver you can:
- Manage your Salesforce data in real time.
- Download data to any application that supports ODBC. (SQL Server or Microsoft Office, for example.)
- Query Salesforce using SQL or SOQL.
- Create an archive of all of your Salesforce data.
The driver distribution includes two drivers, one which supports SQL and one which SOQL. If you want to use the SQL-based driver, you define an ODBC data source for that driver. If you want to use the SOQL-based driver, you define an ODBC data source for that driver. If you want to choose between a SQL-based and a SOQL-based solution, define a data source for each driver.
Easysoft's Salesforce ODBC driver enables you to give your Business Intelligence tools, dashboards, or data warehouse fast, direct, real-time access to your Salesforce data, enabling you to gain deeper insight into this data and help gain competitive advantage.
Product description
Our Salesforce ODBC driver allows applications that support ODBC to get data quickly and easily into and out of Salesforce.
Example applications include Microsoft Office (Access, Excel and so on), OpenOffice, Crystal Reports, Cognos BI, Oracle, and SQL Server.
Typical uses of the Salesforce ODBC driver include:
- The use of SOQL or SQL to select and modify objects in Salesforce.
- Reports that join local tables with Salesforce objects.
- Stored procedures for two-way integration between ODBC-compliant applications and Salesforce.
- Making an archive of Salesforce data.
- Creating new datasets with data from Salesforce and other data sources.
Salesforce ODBC driver benefits include:
- Use any 32-bit or 64-bit application that supports ODBC to gain insight into your business.
- Potentially lower support costs if your developers already use ODBC.
- Establish a secure connection to your Salesforce data.
- Lets you define company specific reports based on real-time data.
- Convenience of permanent or subscription-based licensing.
Prerequisites
As our driver needs to use the Salesforce SOAP API, you need to have access to the Enterprise Edition, Performance Edition, Unlimited Edition or Developer Edition of Salesforce. Some Professional Edition organisations may also have the API enabled. If you need to upgrade your version of Salesforce, please contact your Salesforce account representative.
Your license needs
Server license
For server-side applications and web servers running on UNIX, Linux, or Windows, we offer a permanent machine based license.
Desktop license (annual subscription)
For Windows desktop operating systems and desktop applications such as Excel, Access, Word and so on, we offer an annual subscription license.
Demos
Connect SQL Server to Salesforce by using ODBC
)Passing data between Salesforce and SQL Server
Tutorials
Salesforce ODBC driver (SQL Version):
- Access
- Alpha Anywhere
- Arcplan
- Birst
- DB2
- Excel
- Extreme Translator
- GO
- Jaspersoft
- Logi INFO
- Oracle
- Oracle Business Intelligence Enterprise Edition (OBIEE)
- PHP
- Power BI
- QlikView
- RazorSQL
- SAP BusinessObjects
- SAP Crystal Reports
- SAS JMP
- SPSS
- SQL Server
- Tips for using SQL Server with Salesforce
- SQL Server Reporting Services
- Tableau
- TARGIT
- TIBCO Spotfire
- Yellowfin
Salesforce ODBC driver (SOQL Version):
Platforms
The Easysoft ODBC-Salesforce Driver is currently available on these platforms:
Version | Platform | Distribution |
---|---|---|
v2.1 (Salesforce) | Linux (x86) (64 - Bit) | (kernel 2.6-5.0+, glibc 2.3.5+) |
v2.1 (Salesforce) | Windows (x86) (32 - Bit, 64 - Bit) | (7, 8, 2012 R2, 10, 2016, 2019,11,2022) |
v1.1 (Salesforce) | Linux (ARMv71) (32 - Bit) | (Raspberry Pi, kernel 4.9.41-v7+, glibc 2.24+) |
v1.0 (Salesforce) | AIX (PPC) (32 - Bit) | (4.3-7.2) |
v1.0 (Salesforce) | AIX (PPC) (64 - Bit) | (5.0-7.2) |
v1.0 (Salesforce) | HP-UX (Itanium i64) (32 - Bit) | (11i) |
v1.0 (Salesforce) | HP-UX (Itanium i64) (64 - Bit) | (11i) |
v1.0 (Salesforce) | Linux (Itanium i64) (64 - Bit) | (kernel 2.4-3.0+, glibc 2.2.5) |
v1.0 (Salesforce) | Linux (x86) (32 - Bit) | (kernel 2.2-3.0+, glibc 2.1+) |
v1.0 (Salesforce) | Solaris (Sparc) (32 - Bit) | (2.6-2.11) |
v1.0 (Salesforce) | Solaris (Sparc) (64 - Bit) | (2.8-2.11) |
v1.0 (Salesforce) | Solaris (x86) (32 - Bit) | (2.8-2.11) |
v1.0 (Salesforce) | Solaris (x86) (64 - Bit) | (2.8-2.11) |