Based on the knowledge sources, your issue with

edr report

not pointing to the right database could be related to several factors: 1. Profile Configuration: The most common reason for this error is that your

elementary

profile in your

profiles.yml

file isn't correctly pointing to the schema where your Elementary tables were created. The CLI needs to find the Elementary schema to generate reports. 2. Athena-specific Configuration: From one of the examples, I can see that someone using Athena had a similar issue. They installed the Athena-specific package with

pip install elementary-data[athena]

but still encountered errors when running

edr report

[Slack forum discussion](https://slack.com/archives/C02CTC89LAX/p1700509560573959). 3. Version Compatibility: As you mentioned, there could be version compatibility issues. One user noted: "the problem was also that I was using an incompatible edr version with elementary dbt package" [Slack forum discussion](https://slack.com/archives/C02CTC89LAX/p1693995794537679). To resolve this issue: 1. Ensure your

elementary

profile in

profiles.yml

correctly points to the schema where your Elementary tables were created. The CLI always searches for the schema you specify in the

elementary

profile, regardless of any custom schema configurations. 2. Make sure you've run

dbt run -s elementary

at least once to create the necessary tables. 3. Check that you're using compatible versions of the Elementary dbt package and the EDR CLI. 4. If you're using multiple environments or databases, you might need to specify the target when running the command:

edr report --profile-target <target_name>

. If you continue to have issues, sharing your

profiles.yml

configuration (with sensitive information removed) and the full error message would help in diagnosing the problem further. I hope this helps! Lucy Kafanov