This message was deleted.

Based on the information in the knowledge sources, here are some steps and considerations to help resolve your issue with GoodData querying the wrong schema: 1. Check LDM-to-Database Mapping: Ensure that each dataset in your Logical Data Model (LDM) is correctly mapped to the intended table in the correct schema. In GoodData, you can do this by: - Selecting a dataset in the LDM modeler. - Going to the Data mapping tab. - Verifying that the table and schema referenced are correct. - Saving any changes you make. Repeat this for every dataset in your LDM to ensure all mappings are correct. [Map the LDM to the Database](https://www.gooddata.com/docs/cloud/model-data/create-logical-data-model/create-ldm-manually/#map-the-ldm-to-the-database) 2. Review Data Source Configuration: GoodData sets the database connection context to the schema defined in the data source configuration. If your data source is configured to use Schema B, GoodData will default to that schema unless you fully qualify table names in your mappings or SQL datasets. [Create SQL Datasets](https://www.gooddata.com/docs/cloud/model-data/create-logical-data-model/create-sql-datasets/) 3. Schema Referencing in SQL Datasets: If you are using SQL datasets, remember that objects from the default schema (as set in the data source) do not require schema qualification, but objects from other schemas do. If your queries are running against the wrong schema, double-check the schema setting in your data source and the references in your SQL queries. 4. Changing Data Source or Schema: If you need to change the data source or schema for your workspace or datasets, you must update the mapping in the LDM and ensure you save the changes. If you only change the data source dropdown in the LDM modeler but do not save or properly map each dataset, the change may not persist, and GoodData may continue to query the old schema. [Community Slack Discussion](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1738595444313339?thread_ts=1738595444.313339&cid=C04S1MSLEAW) 5. Cache Considerations: Sometimes, GoodData may show cached results. If you have recently changed the schema or data source, try clearing the cache to ensure you are seeing the latest data and queries are being run against the correct schema. [Cache Management](https://www.gooddata.com/docs/cloud/connect-data/cache-management/reload-cached-data/) Summary of Actions: - Double-check and update the dataset-to-table (and schema) mappings in your LDM. - Verify the schema set in your data source configuration. - Save all changes in the LDM modeler. - Clear the cache after making changes. - If using SQL datasets, ensure schema references are correct. If after these steps the issue persists, please provide more details such as screenshots of your LDM mappings and data source configuration, as this will help further diagnose the problem.