Attention, Google Cloud Platform BigQuery users!

Implications of BigQuery Studio launch

As a part of the BigQuery Studio launch, BigQuery will be enabling additional services in your projects. These changes will provide you with additional analytics platform capabilities without requiring admins to enable the services individually for each project.

What will change?

  • Automatically enabled APIs to help with code development (Dataform), data governance (Dataplex and BigQuery Data Policy), data access and sharing (BigQuery Connection and Analytics Hub), and workload management (Reservations API).
  • The existing, “classic” saved query experience will be replaced, starting with changing a policy (roles) and permission for new queries and notebooks.

Do you need to take action?

API enablement
Some of our clients have already enabled the mentioned APIs. Using these upgrades makes your way of working with data more efficient regarding Data Quality and Data Management. So, if you are open to new things, you don’t need to do anything. Check the possibilities and consider implementing them into your current workflow. And, of course, check the billing for some time to monitor any changes.

If you think this is not the right moment, and you are not ready to work with automatic enabled API’s, it’s possible to ask Google Support or us not to enable them or turn them off by themselves after 3rd March 2024.

Query migrations

It’s a long-term process that starts now. However it is important to remember that working with saved queries as you do right now, might change regarding permissions and migration.

→ By 2025 in order to edit your “classic” saved queries and access the new features, you must save your “classic” queries as new saved queries, either manually or with a new batch-conversion tool to be launched by June 2024. Classic saved queries will be automatically updated to a new one by March 1, 2025. You may need to grant additional permissions to ensure users can access the new saved queries. Google will not delete these queries.

→ If you have sensitive data information queries, the query owner should delete the queries or remove the sensitive information before the end of March 2025. All queries will be automatically converted to the new saved ones at that time. It is recommended to keep an eye on the updates.

If you need any help with the implementation of the changes above, do feel free to reach out to us and we’re more than willing to help you out.

More To Explore