Datasource-signon-schema name stock

[jive]

Hi,
I have a big problem here, when you define a single signon in a datasource and you import the table from a database schema, example schema_1, the name of the database schema where you have picked the metadata is stock somewhere with the metadata definition.
My problem is between development and Q&A platform the database schema name have change due to some new security restriction.

Is there a way to modify the schema name in the metadata without having to do a new import the metadata again.
OR
I will have to re import everything and rebuild everything.

Thanks for your help

[Lynn]

In Framework Manager there is a schema property associated with a data source. You can leave it out altogether if the connection to your database will understand what schema to use.

Select * from MyTable
vs.
Select * from schema_1.MyTable

If you MUST have a schema name then you will have to change it when you migrate. Better yet, use a parameter map to set the correct schema name based on a query to the system tables. I use this approach for DB2 because they require me to prefix all table names with the library (schema) name.

[jive]

Thanks Lynn for your answer,

Did I have to set this value in the sessions parameter and apply it to the query subject or elsewhere.

thanks

[Lynn]

There is a folder in your FM project called "Data Sources". Select the datasource in question and you will see the Schema property for that source. This is what you need to change.

The easiest solution is to simply remove this property if your database query will be correct without the schema prefix. What DBMS are you using?

In my case the schema property is a macro referring to a parameter map based on a query of the system tables. Attached is a document I wrote up explaining the approach. As I said, it would be easier if the connection to the database could just sort things out for you on the database side rather than going through this nonsense....

As a side note (to file away for future reference), this same approach can be used in a scenario where you have an active data mart and a load data mart and Cognos needs to flip between them. You just need a separate independent place that can tell you which is active (e.g., something the ETL sets) and then use that as the basis for the parameter map.

[jive]

Thanks a lot ,
I resolve everything now.
you save my day  ;D

[Lynn]

 :)