Skip to Content
Author's profile photo Raghunathan Balasubramanian

Alias and their application during runtime


There is an increasing number of scenarios where the database schema that is connected to using Business Objects Data Services in databases like ORACLE and SQL Server change from one environment to another. For example, an ORACLE Schema called DEV_PRJ1 can be assigned to datastore for development repository and TST_PRJ1 can be assigned for test repository. In case of development there is also a possibility that there are multiple development database schemas are available so that each developer in a multi-user environment is assigned a specific database schema associated to their repository which will provide the ability to perform unit testing in a more realistic fashion. So there can be database schemas like DEV1_PRJ1, DEV2_PRJ1, DEV3_PRJ1, and so on each being a database schema that can be connected through a different BODS Repository assigned to an user for development and unit testing.

In such cases there is a need to have a consistent naming convention to ensure that the database objects’ metadata like table, views, etc, that are imported into one BODS repository can be consistent when the code is exported to another repository. In such cases the use of Aliases in datastore come in handy.

Alias Fig1.jpg

In Fig1 above, a database schema ABC is assigned to alias DBO for a MS SQL Server datastore. In this case, the schema name dbo is the standard schema that is used in environments like pre-production and produciton where there will be a single database to host the data for the BODS objects to connect to during runtime. However there can be multiple schemas defined under a single database in dev and test environments to cater for parallel development and testing to enable delivery.

Do please provide feedback on adding any more information that can be of use in this context.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      This is very useful. Can you also provide information on configurations and system configs so that we can have a single document with all info?

      Author's profile photo Sharath Ravindranath
      Sharath Ravindranath

      Even though this post is a bit old, trying my luck to get the answer to my query below -

      How would you handle the scenario where multiple data base schemas in same database assigned to same user. (associated with a single repository). Would like to know how the alias feature should be used in this case. To elaborate with an example -

      Multiple database schemas could be used such as DEV1_PRJ1, DEV2_PRJ1, DEV3_PRJ1  (as in the above explanation) within same database. Now the user needs to import all the tables belonging to different schemas/owners into his repository. When the user is migrating his jobs to production, how should the alias be set.?

      Alias Dev_config Prod_config
      DBO DEV1_PRJ1

      Where should the other Schemas such as DEV2_PRJ1 and DEV3_PRJ1 to be defined ? (Unable to create more than one alias with same name in data store configuration).

      Please let me know how to handle this situation. Thanks.

      Author's profile photo Raghunathan Balasubramanian
      Raghunathan Balasubramanian
      Blog Post Author

      Can you send a screenshot of the issue so I can have a look?

      Author's profile photo Sharath Ravindranath
      Sharath Ravindranath

      There are two database schemas that are imported into same BODS repository in Dev environment, namely; ABC and DEF. I want to map both the schemas to one single owner in the Production environment as “DBO”.

      How Is this possible ?

      Cant create two Aliases with same name (DBO) in data store. It is throwing error. (Able to create DBO and DBO1). Please let me know how this can be handled.


      Author's profile photo Raghunathan Balasubramanian
      Raghunathan Balasubramanian
      Blog Post Author

      Hi If you need the same datastore to point to two separate databases then two separate configuration will do the job. You have DS_DEV_Env as a configuration. Create another configuration and add the DEF database to it.

      If however you need these two databases under the same datastore configuration in a single datastore, it will need two separate aliases.