Warehouse and analytical

BigQuery

BigQuery uses GoogleSQL, project/dataset/table metadata, dry-run estimates, job timelines, slot and reservation posture, and guarded cloud-operation previews.

Available for Prometheus HTTP queries and bounded exports12 minDesktop

Prerequisites

Install the current DataPad++ desktop pre-release on Windows, macOS, or Linux.
Have the endpoint, database file, or cloud account details for a BigQuery datastore you are authorized to use. Start with least-privileged, read-only access.
Keep an independent backup before enabling edits, administration, restore, or transfer execution.

Connect and run a safe query

1
Create the connection
Open Library, choose Create connection, and select BigQuery and a supported Connection method tab.
2
Test and save
Complete the applicable fields and enable Read-only connection. Test connection when available; new local files and pending secondary credential changes must be saved first. Review runtime limitations and warnings.
BigQuery connection setup. The BigQuery connection dialog with supported method tabs and illustrative, non-secret settings. Expand optional sections and review runtime limitations before saving. Open full size
3
Open the native explorer
Use Save Connection, or Create Database and Save Connection for a new local file, then open the BigQuery Explorer where supported.
4
Select a scope
Select the database / schema scope that should be attached to the new tab.
5
Run a bounded read
Open a query tab, paste the bounded read-only sample below, and choose Run or press Ctrl/Cmd+Enter.
BigQuery native workflow. A representative BigQuery explorer and bounded read-only workflow. Replace the example objects with names from your datastore. Open full size
6
Inspect the result
Inspect Results, Messages, History, and Details; dock the panel on the bottom or right as needed.
7
Export when needed
Export only the required rows after reviewing format, destination, and redaction options.
8
Open diagnostics or transfers
Open Diagnostics or Transfers from the drawer/status bar and treat disabled reasons as capability boundaries, not transient errors.

Connection fields

Field	Required	Purpose	Safe example
Name	Yes	A clear profile name, without credentials.	BigQuery development
Connection method	Yes	Choose a supported tab. The fields below apply only to the selected method and deployment.	Cloud / endpoint settings / Connection string
Environment	No	Attach the intended variable and safety context.	Local development
Read-only connection	No	Enable for initial exploration. This does not make pre-release software safe for production workloads.	Enabled
Host / Port	No	Endpoint for a fields-based connection. Follow the selected deployment and runtime limitations; MongoDB SRV does not use an explicit port.	localhost / engine default
Database / default scope	No	Initial scope for browsing, where supported.	catalog
Complete connection string	Yes	Required in Connection string mode only. Saved unchanged as one vault secret with Save Connection. Blank keeps an existing stored value.	Paste your complete provider string; do not share it
Username	No	Authentication identity for the selected method.	catalog_reader
Password	No	Required only when the chosen authentication needs it. Save Connection stores changes; blank preserves an existing value, and Reveal… explicitly discloses it.	Stored in the desktop OS vault
Contract endpoint	No	General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Account	No	General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Project	No	General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Dataset	No	General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Database	No	General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Schema	No	General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default

Run the sample query

BigQuery read-only example

SELECT order_id, customer_id, total
FROM `demo.analytics.orders`
ORDER BY order_id
LIMIT 25;

Explore and inspect

Browse projects, datasets, tables, views, jobs, reservations, scheduled queries, copy jobs, access, storage, slots, and diagnostics.
Inspect result grids, dry-run totalBytesProcessed, job timeline rows, slot usage, reservation posture, raw REST payloads, and cost warnings.

Diagnose, administer, and transfer

Review jobs, job timelines, slot usage, reservations, cost/storage posture, access, dry-run estimates, scheduled queries, and cloud auth disabled reasons.
Preview table copy/clone, scheduled query, reservation, access, cloud import/export, load/unload, and guarded drop workflows.
Import — Plan only. BigQuery uses managed load and extract jobs through Cloud Storage. Formats: CSV (portable-lossy), NDJSON (portable), Avro (native), Parquet (native). Destinations: cloud uri. Live BigQuery transfer requires authenticated Jobs and Cloud Storage APIs plus opt-in validation against a real Google Cloud project.
Export — Plan only. BigQuery uses managed load and extract jobs through Cloud Storage. Formats: CSV (portable-lossy), NDJSON (portable), Avro (native), Parquet (native). Destinations: cloud uri. Live BigQuery transfer requires authenticated Jobs and Cloud Storage APIs plus opt-in validation against a real Google Cloud project.
Backup — Plan only. BigQuery uses table copies, snapshots, and clones. Formats: Native managed backup (native). Destinations: managed restore, cloud uri. BigQuery copy, snapshot, and clone recovery require authenticated Jobs APIs, an isolated destination, and opt-in validation against a real Google Cloud project.
Restore — Plan only. BigQuery uses table copies, snapshots, and clones. Formats: Native managed backup (native). Destinations: managed restore, cloud uri. BigQuery copy, snapshot, and clone recovery require authenticated Jobs APIs, an isolated destination, and opt-in validation against a real Google Cloud project.

Transfers Center. Transfers Center shows a failed example transfer with its warning count, failure detail, retry control, and dismiss action. — **Transfers Center.** Transfers Center shows a failed example transfer with its warning count, failure detail, retry control, and dismiss action. Open full size

Capabilities and availability

Capability	Status	Notes
Native explorer	Available	Browse projects, datasets, tables, views, jobs, reservations, scheduled queries, copy jobs, access, storage, slots, and diagnostics.
Read queries	Available	Run scoped GoogleSQL, table SELECT builders, deterministic IntelliSense, bounded query starts, dry-run request payloads, and job-aware query previews.
Inline editing	Unavailable	Use a reviewed statement or the engine-native tool instead.
Diagnostics / administration	Guarded	Preview table copy/clone, scheduled query, reservation, access, cloud import/export, load/unload, and guarded drop workflows.
Import / export / transfer	Guarded	Availability follows the authoritative runtime transfer manifest and shows a disabled reason when execution is not implemented.

Safety and limitations

Troubleshooting

Symptom	Resolution
Test connection fails or times out	Verify endpoint, port, TLS mode, proxy settings, service health, firewall rules, and network access. Keep the profile unsaved until the test explains the failure.
Explorer branches are empty or disabled	Confirm the selected database / schema, refresh the branch, and grant the minimum metadata permissions described in the connection warning.
Run, edit, admin, or transfer is disabled	Read the visible disabled reason. Select a compatible target, turn off read-only only when authorized, or use the documented preview/export fallback.
The sample query fails or returns different columns	Replace the example names with objects from your BigQuery datastore, confirm the selected database / schema, and keep the query bounded while you validate the result.

Prerequisites

Create the connection

Test and save

Open the native explorer

Select a scope

Run a bounded read

Inspect the result

Export when needed

Open diagnostics or transfers