Ways to run SQL queries on Oracle Fusion Cloud, and which to use
You cannot connect a SQL client straight to the Fusion Cloud database, so every route to your data goes through a reporting or integration layer. This guide compares the main options and says when each one fits.
The short answer
Oracle does not generally expose the Fusion Cloud database to customers. To run SQL, the supported route is a BI Publisher data model with a SQL data set. Other routes, such as OTBI, BI Cloud Connector extracts and REST APIs, answer different needs and do not run table-level SQL the same way.
The options side by side
| Option | What you write | Best for | Main limits |
|---|---|---|---|
| BI Publisher data model (SQL data set) | SQL against Fusion tables and views | Ad-hoc queries, reports, data checks | Read-only (SELECT). Slow edit-run loop in the browser. Needs BI Publisher access |
| OTBI analyses | Drag-and-drop, or logical SQL over subject areas | Business reporting without SQL | Works on subject areas, not on the physical tables and views |
| BI Cloud Connector (BICC) extracts | Choose view objects to extract to files | Bulk loads into a data warehouse | Scheduled file extracts, not interactive queries |
| REST APIs | HTTP requests | Integrations and transactions | Not SQL. Returns business objects, not table rows |
| Developer tools that use the BI Publisher report service | SQL in an editor | Faster interactive SQL development | Same read-only SQL and the same privileges as your account |
Which one should you use?
- Answering a one-off data question about tables: a BI Publisher data model, or a developer tool that runs the same SQL from an editor.
- Reports for business users: OTBI, or a BI Publisher report.
- Feeding a warehouse or lake: BI Cloud Connector extracts.
- Creating or changing data: the application, REST APIs or file-based loaders, never SQL.
Why the browser route is slow
With a BI Publisher data model you paste SQL into a data set, save, run the report and open the output, then repeat for every change. There is no autocomplete, so people keep a tables reference open in another tab. How to run SQL against Oracle Fusion from VS Code shows how a developer tool shortens that loop.
What does not change with any tool
- Privileges. You see only the data your Fusion account is allowed to see.
- Read-only SQL. BI Publisher SQL data sets read data. They do not insert, update or delete.
- Performance rules. Heavy queries still need filters, sensible joins and care with large tables.
Read Fusion SQL security and privileges before choosing a tool that handles your credentials.
Frequently asked questions
Can I connect SQL Developer directly to Oracle Fusion Cloud?
Oracle does not generally expose the Fusion Cloud database to customers. The supported routes are reporting and integration services, such as BI Publisher, BI Cloud Connector and REST APIs.
Can I run INSERT, UPDATE or DELETE on Fusion tables?
No. SQL in a BI Publisher data set is for reading data. Change data through the application, supported APIs or file-based loaders.
What is the difference between OTBI and BI Publisher SQL?
OTBI works over subject areas and uses logical SQL. A BI Publisher data model with a SQL data set queries physical Fusion tables and views directly.
Is FuiSQL the only tool that does this?
No. Other third-party tools also run SQL through BI Publisher. This guide describes the options by category, and FuiSQL is one example of a developer tool.
Run SQL against Fusion from VS Code. FuiSQL has a free trial.
See FuiSQL Get it from the VS Code MarketplaceRelated guides
FuiSQL is an independent product by FuiSQL. Oracle and Fusion are trademarks of Oracle and/or its affiliates; FuiSQL is not affiliated with, endorsed by or sponsored by Oracle.