![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi all, We use Microsoft Analysis Services using an Oracle Database as Data Source. We should be able to change from the production database-schema to the development database-schema (and back again). In the data source definition, the user (schema) and password are provided. When we design our cubes based an the (development) data source, AS puts the shema name in the definition of the tables and source columns. E.g.: "AT_PUBLISH_DEV"."PM_GEOGRAPHIES" is our "Geographies" table, "AT_PUBLISH_DEV"."PM_ACTIVITIES"."ACT_CALLS" is the source column for our "Calls" measure. If we want to change the datasource to use the "AT_PUBLISH_PRD" database schema instead, we get conflicts cause AS obviously can't find the "AT_PUBLISH_DEV"."PM_GEOGRAPHIES" table. How can this be solved without having to create a separate AS database and (manually) re-create the AS objects? Is there a way to tell Analysis Services NOT TO USE these "Fully qualified table names", to ommit the schema name? Thanks for any suggestions, Francis. |
![]() |
| Thread Tools | |
| Display Modes | |
| |