Acumatica SaaS ODBC Database Access Retirement
Effective March 31, 2019
ODBC database access is being retired for SaaS customers effective March 31, 2019. Customers using a private cloud will still be able to use this feature.
Why is ODBC being retired?
Acumatica is phasing out ODBC as part of the ongoing efforts to provide the highest possible security and compliance for SaaS customers. ODBC is an older technology and there are better, more secure alternatives with the Acumatica technology platform to ensure customer data is securely stored in the application database.
Alternatives to ODBC
The most common use of ODBC is for pulling Acumatica data into reporting tools such as SQL Server Reporting Services. The table below lists some alternative options for retrieving Acumatica data.
|OData||The Open Data Protocol (OData) provides a secure way to expose Acumatica through a set of RESTful APIs. By using generic inquiries, you can expose specific data to external systems and assign specific security permissions to the consumers of this data. ODBC does not provide this level of security which is often required for compliance standards.
|APIs||Acumatica APIs allow external applications to securely retrieve Acumatica data. Unlike ODBC, APIs require Acumatica login credentials so specific access permissions can be granted and revoked from inside the application – a key requirement for many compliance standards. Acumatica contract APIs provide versioning so you can more quickly adapt data consumption to application changes.
|Internal Reporting||Acumatica provides internal reporting tools (generic inquiries, pivot tables, analytical report writer) to analyze data directly within the application. Generic Inquiries (GIs) feed data to dashboards, business events, external systems via OData, and pivot tables for immediate action, notification, or data analysis. External data can be made available to GIs using simple customization techniques.
|Private Cloud||Customers who require ODBC access may opt for a private cloud deployment via a subscription or perpetual license. The private cloud can be secured according to the client’s needs and engineered to support required service levels.