BigQuery

Welcome to the Google BigQuery idea forum. You can submit and vote on ideas here to tell the Google BigQuery team which features you’d like to see.

This forum is for feature suggestions. If you’re looking for help forums, look here:

We can’t wait to hear from you!

  1. Allow us to use Multi-byte characters for table name and column name!!

    Most countries are not common for English. In such a country, most datasets which users want to store in BigQuery are written by Non-English, for instance, columns and table names. Ex, Japanese, Chinese, Spanish, German etc...

    Currently, users have to translate or remember each English columns to their mother language for composing sql queries and exploring entire datasets on BigQuery windows.

    These annoying experience is NOT smart and we believe Google Cloud will save such ignored users in very near future.

    67 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Have an option to automatically backups tables that are in BigQuery.

    Instead of having to do it manually, it would be good to have an option that automatically backups tables that are in BigQuery (it could be done on a daily basis or monthly basis). The backups could be stored on Cloud Storage or another place.

    57 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. Transfer Dataset across projects

    Ability to transfer an entire dataset to a different project.

    Possible Solutions:

    1. An option saying transfer dataset to a specific email address where the new owner decides to which project the dataset needs to be added.

    2. A "Copy Dataset" option which copies all tables in a dataset to a different project. In this case, the current user needs to have the associated required permissions for both the projects to do the same.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Multiple Query Editor tabs

    It would be useful to be able to have multiple query editor tabs open in the web UI

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  6. Ability to use Cloud SQL (postgres and mysql) as External Tables

    Currently we push many tables from relational stores, which hold dimension data, into BigQuery. Being able to push a subquery out to these databases on demand eliminates lag and a whole lot of ETL work.

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. Have option to grant access for Views at a Dataset Level rather per view.

    Currently the options to give access to BQ Datasets via views is rather limited. It also requires a lot of maintenance if you want to create new views looking at the same dataset(s) / table(s). I propose a kind of "WITH GRANT OPTION" permissions which allows you to set read access on a dataset that will allow any views created in that dataset to view data in the dataset which access was granted for.

    Example:

    DS1 has tables only.
    DS2 has views that point at tables in DS1.
    I would grant read access ON DS1 TO DS2 WITH GRANT OPTION.

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Have a better documentation on api clients

    I wanted to connect my NodeJS server to BigQuery, but the NodeJS client api seems quite sparse with indication of how to connect an app or server to BigQuery. The tutorials are also not linear or straight forward, they seem to have random bits of examples but no concrete example.

    The stack-overflow channel and BidQuery forum doesn't answer that.

    In my case I have a NodejJS server running in a container engine and have no clue how to map it to BigQuery. There's also Cloud SQL but it doesn't scale to my needs.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  9. Ability to download/view query history as BigQuery table

    So far I have to use the rest API to get query history and do some usage analytics on it. It would be much easier to expose the usage history as special table or provide ability to export query history as csv or BQ table

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. add shorthand for cast(), like table.column::INT64

    we used the shorthand for cast (::) extensively in postgres and redshift, would be great to retain the increased readability

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Create a PDO Connector

    Provide connection through PDO so PHP clients can use standard software that supports this connection method. This would be a great addition to the StandardSQL support and would enable a ton of software to use BigQuery as their DB backend.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. specify output format for Save Results > CSV

    The BigQuery UI currently does not allow you to specify the layout of .csv export files. Would be great if there's some extra options, specifically:

    * choose the delimiter (comma, semicolon, tab, pipe, other/specify)
    * choose the enclosing character (double quote, none)
    * include/exclude headers
    * include/exclude leading rownumber column

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Query Google Storage objects from BigQuery

    Be able to select attributes from Google Storage, like folder or file size, etc.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. We need to push and pull capability between every GCP datasource (and external parties) and Bigquery

    Right now, it is a little big of a hodge podge of what can easily talk to what. For example, you can't easily get from BigQuery into CloudSQL or vice versa. It generally takes 2 steps instead of 1 (Export to GCS, then import into Postgres). Part of this task is to make sure GCP has robust ODBC/JDBC drivers for BigQuery that can allow most any database on the planet to connect into BigQuery

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Ability to use Cloud Spanner as import datasource

    Cloud Spanner have high availability performance, but storage cost is high than bigquery.
    I want to save data after ETL processing to BigQuery storage.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  16. Paid Plan for Extending Upper Quotas of daily "create-table".

    Currently, users can create a table 1,000 times a day in one GCP-project.
    However, sometimes we need more than its limits.
    Please prepare extending option for upper limit with paid plan such as like NLP api charging.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. A way to automatically migrate schema description and table details to other tables.

    Right now, when you create a copy of a table, it takes the existing schema but does not carry over any of the descriptions or table details. For large numbers of columns it is slow and annoying to have to re-enter all those details. A copy schema function or tool would be great.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  18. Ability to export the table to datastore

    It would be great to have ability to transfer BQ database to Datastore.
    Example use case: we have a table which was used for mostly write-only audit logging with rare analytics queries. But now we need to read from it quite often, so Datastore is more suitable for the task

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Add a "Refresh Tables" option in the new web UI, just like we had in the old one.

    It is so annoying to have to fully refresh each open web UI as you add new tables.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. When saving result tables, remember where last table was saved

    I had an exercise where I needed to query one table multiple times describing more specific data sets based on certain values. Every time i save my resulting query table, I have to go back and respecify the destination project that I am saving it to, which is tedious; especially when I save it to the wrong predetermined spot by accident and need to delete it. Please add a small feature that remembers the last project a dataset was saved to.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

BigQuery

Feedback and Knowledge Base