[federate-bq-to-alloydb]

[duncmon]

Step 6 line 3:
"Once connected, on the Query Editor tab on the right side, enter the following statements and RUN one by one:

CREATE EXTENSION IF NOT EXISTS  bigquery_fdw;

CREATE SERVER bigquery_server FOREIGN DATA WRAPPER bigquery_fdw;

CREATE USER MAPPING FOR postgres SERVER bigquery_server;

"

The first command "CREATE EXTENSION IF NOT EXISTS bigquery_fdw;" is likely to fail if the flag "bigquery_fdw.enabled" is "on" has not been set on the instance.
This can be done from the AlloyDB Overview page:

1. Scroll down to "Instances in your cluster"
2. For your instance (default naming is likely to be "my-primary-inst") click on the 3 dots and select "Edit"
3. Scroll down to "Advanced Configuration Options" and click on this to show them
4. Find "Flags" and click on "Add a database flag"
5. Under "New database flag", "Choose a flag" enter "bigquery_fdw.enabled" and give it the value "on"
6. Click on "Done"
7. Click on "Update instance"
8. Wait a few minutes for the instance to be updated

Return to the Query Editor tab in AlloyDB studio. Once updating is finished, try running the "CREATE EXTENSION IF NOT EXISTS bigquery_fdw;"command again. The command should execute successfully if the instance has finished updating. Continue with the codelab.