SuiteAnalytics Connect (SAC) is Oracle NetSuite's optional ODBC and JDBC service for connecting external tools to NetSuite data. It costs approximately $499 per month per concurrent connection ($5,988 per year) and is required by ODBC-based connectors including the Microsoft Power BI native NetSuite connector, Fivetran, CData, and most legacy BI tools.
What SuiteAnalytics Connect provides
- ODBC driver for connecting Windows applications (Power BI Desktop, Excel, Tableau Desktop, SSIS, custom apps).
- JDBC driver for Java-based tools (Tableau Server, MicroStrategy, Domo, Looker on-premise).
- Connect Schema — a flat, denormalized view of NetSuite data optimized for reporting (different from the live transactional schema).
- SuiteAnalytics Workbook UI for ad-hoc analysis directly in NetSuite.
Why it costs so much
SuiteAnalytics Connect was Oracle's primary integration path for years before SuiteQL matured. Pricing reflects that legacy positioning: per-concurrent-connection licensing, billed annually or monthly. A single workstation costs $499/month. Five analysts running Power BI Desktop concurrently? $2,495/month. Add a load-balanced gateway for production and the bill keeps growing.
When you still need SuiteAnalytics Connect
- You're using Power BI Desktop's native NetSuite connector (it's ODBC under the hood).
- Your ETL platform is Fivetran, CData, or any ODBC-only connector with no SuiteQL support.
- You rely on SuiteAnalytics Workbook directly in NetSuite for ad-hoc reports.
- You have legacy SSIS, Informatica, or on-premise BI infrastructure that only speaks ODBC.
When you don't need it
If you're using a modern NetSuite connector built on SuiteQL via REST APIs, you skip SAC entirely. Acterys NetSuite Sync, for example, uses OAuth 2.0 and SuiteQL natively to populate Power BI, Snowflake, SQL Server, BigQuery, and Azure Synapse without ever touching ODBC. Customers report saving the full $5,988/year while gaining better performance and easier setup.
Is SAC's denormalized schema worth $5,988?
SAC's main technical selling point is its pre-built denormalized "Connect Schema" optimized for reporting. The trade-off: you pay $499/month for a schema you could rebuild yourself in 30 minutes of SuiteQL with custom JOINs. Modern SuiteQL connectors do this automatically and ship pre-built star schemas tuned for Power BI and Snowflake, eliminating the schema rationalization argument for SAC.
How to evaluate switching
- List every tool that currently connects via SAC. Power BI, custom Excel sheets, scheduled SSIS jobs, etc.
- Check whether each tool supports SuiteQL via REST. Most modern BI tools do, often through a community connector or a SaaS layer like Acterys.
- Run a 14-day parallel test. Both SAC and the new SuiteQL connector pull the same data. Validate row counts, totals, and schedule timing.
- Cancel SAC at next renewal. Most contracts allow non-renewal with 30 days notice.
Related glossary entries
- SuiteQL — the modern alternative to SAC.
- ODBC — what SAC actually uses under the hood.
- MAR Pricing — Fivetran's volume model that compounds with SAC costs.