what is the difference b/w the public object&schema object
Answer Posted / sunil
Well both the above answers are correct, they both told one one part.
Schema OBJ: those object which are being accessed by the architect only which is granted by the admin. and in the formation of basic architect of any project they play very important role, as they directly deals with the structure and data information in back-end i.e data warehouse. this one reason why we have to update them once changed.
where as
Public OBJ: they are accessed by the report developer only but as per requirement admin may grant you access in schema obj as well. These object are generally used to develop any report since they are not playing any role in architect of the project or the basic object so they dont't required update if any changes are done. public objects are generally created over the schema obj.
| Is This Answer Correct ? | 13 Yes | 0 No |
Post New Answer View All Answers
Now, imagine this, you come across a situation where an aggregate table at higher level has a higher lts than the one at lower level. A.) What problems can you anticipate? B.) How would you solve the problem.
What happens if the owner of an object does not exist in the destination project?
Can intelligence server integrate with my existing data structure?
what do you mean by kimball?
Is olap services sold as a separate product?
Explain object variable error?
What do you mean by consolidations?
Write the components microstrategy metadata?
What do you mean by staging area?
Explain level extension?
Explain the various types of filters available.
Explain standard filters?
what do you mean by custom groups?
What are pass-through functions and why they are so called? Give some examples.
Compare dataset and fileset?