Hello! I upgraded two BigQuery destinations on Airbyte cloud to Destinations V2. The problem is, I have one BigQuery destination with EU data residency, and the other in US data residency. Both destinations are in the same BigQuery project. Upon upgrading, the EU destination worked fine, but the US destination is giving an error because the airbyte_internal schema where the raw tables are saved is in EU. How does Destinations V2 handle multiple destinations with different data residency locations in one BigQuery project?

Hmm, I don't know enough to give you a confident answer yet. The provided extracts do not contain specific information about handling multiple destinations with different data residency locations in one BigQuery project after upgrading to Destinations V2. However, it's worth noting that each destination version is managed separately, so if you have multiple destinations, they all need to be upgraded one by one. Also, when you upgrade to a Destinations V2 compatible version of your destination, a copy of your existing raw tables will be left as they are, and new syncs will work from a new copy made in the new

airbyte_internal

schema [source](https://docs.airbyte.com/release_notes/upgrading_to_destinations_v2/). For more specific guidance, I recommend checking the [Airbyte documentation](https://docs.airbyte.com/integrations/destinations/bigquery) or reaching out to the Airbyte community on their [Slack channel](https://airbytehq.slack.com) or [discussion forum](https://discuss.airbyte.io).