I’ve created a universe in BO4.1 SP5 with a connection pointing to DEV database in DEV environment, when it’s promoted to TEST environment and change the connection to point to the TEST database, I expect to see the universe objects with TEST database_name.table_name.column_name but it still shows the DEV database_name.
Note: It’s the same database in both DEV and TEST but with different names. Due to company policies they have to be named different.
Is this a bug in BusinessObjects 4.1 SP5 or is it something that can be fixed by changing some settings in IDT. Can someone please advise?
And your DBMS is? Oracle, MS SQL Server?
Typically, using different schema names (Oracle lingo) for DEV, TEST, PROD databases is a baaaaad idea. You can set up public synonyms (Oracle lingo) to get rid of this issue though (ask your DBA for details, please).
Note: A “Schema” from Oracle is called “database” in MS SQL Server
Nevertheless:
You should be able to select all tables in data foundation in IDT, then right click and choose “rename qualifier” or something along those lines.
But you will have to do that every time you promote your universe, in your scenario.
I am totally with Andreas her with it being a Baaad idea.
Even if the databases are named differently the schemas should be named the same surely, or otherwise it requires workarounds between every level lof the Lifecycle (unnecessary) may I add.
But we should not be here to criticise but to help out as much as possible.
I dont think even using the Promotion Overrides would work in this instance though especially if it has been set up as multi-source universe.
The answer is as Andreas said I am afraid select them and change qualifier name
inside the designer you can actually get rid of the database and or owner prefix.
As long as the tables are unique for your user you should be fine and only see the tables for your environment. This means less maintenance and on fewer possible errors in the future when you promote your universe
Andreas, It’s SQL Server. I don’t know why it’s set up with different database names in DEV/UAT but I’m aware of the option rename qualifier. It manual though and every time we promote the universe this manual task has to be done. I was expecting BusinessObjects to pick up dynamically as it’s the same schema and table names except that the database is named differently.
Is there any other way to do this.
Barky Baloo - The only solution that I know to this issue is manual renaming the qualifier, and to get some advice from the folks I’ve put my issue here.
Mak - If it’s me I wouldn’t design it like that but unfortunately it’s already been designed and it’s resilient to change. I’ve advised it’s a bad practise the moment I’ve noticed this.
Klaus -
Thanks for your advise, I’ll take a look and see if that helps.
I experience the same issue on a multisource universe, with 1 SQL server datasource.
The names of schema is different in DEV/VAL/PROD in my context also, I cannot change the schema name.
In IDT I tried to delete the owner but then all joins disappear… So I conclude IDT must contain an owner to work.
(BOB member since 2009-09-01)
(BOB member since 2002-06-20)
(BOB member since 2005-01-06)