1

I have olap database for both production and test. Fortunately I noticed that cube under both production and test olap database has the same object name and Id. But DataSource for production and test olap database pointed towards different database connections.

My question is, having same object name and Id for the cube under different olap database is a problem or if I process the cube under test, does that overwrites the production cube?

2

Every object has a Name and ID property that must be unique within the scope of the parent collection. For example, two dimensions can have same name as long as each one resides in a different database.

A database is a scope. A cube is an object. Two cubes can have same name or ID as long as they belong to different databases.

Although you can specify it manually, the IDis typically auto-generated when the object is created. You should never change the ID once you have begun building a model. All object references throughout a model are based on the ID. Thus, changing an ID can easily result in model corruption.

DataSource and DataSourceView objects have notable exceptions to naming conventions. DataSource ID can be set to a single dot (.), which is not unique, as a reference to the current database. A second exception is DataSourceView, which adheres to the naming conventions defined forDataSet objects in the .NET Framework, where the Name is used as the identifier.

Naming Conventions

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.