Q. The attributes that can be arranged into hierarchy are called

View solution

Q. The set of all the entities having same attributes is classified as

View solution

Q. The set of values which specifies which values are to be assigned to individual entities is considered as

View solution

Q. The type of attributes that can be divided into smaller parts is classified as

View solution

Q. The particular database and the set of related programs which helps in implementation of updates and queries is called

View solution

Q. The detailed description on entity constraints, entity relationships and entity types is expressed in

View solution

Q. The types of partial constraints are

View solution

Q. The attributes which have only one value for a specific entity are called

View solution

Q. The phase in data designing in which the access paths and database indexes are specified is classified as

View solution

Q. In programming languages, the available data types are

View solution

Q. The kind of constraint which cannot let two entities to have similar values is classified as

View solution

Q. The data model in which the relationships are explained in terms of attributes is classified as

View solution

Q. The first step in designing high level conceptual data model is

View solution

Q. The weak entities and their identifying relationship in the ER diagrams are represented by

View solution

Q. In ER diagrams, the rectangles are used to denote

View solution

Q. In entity-relationship diagrams, the participating entities are represented by

View solution

Q. The relationship type in which one attribute is migrated to the N-side of relationship is classified as

View solution

Q. The entities that have key attributes to be distinct are considered as

View solution

Q. The schema which specifies that all the database users requirements have been met is called

View solution

Q. For a relationship type, the participation constraints and cardinality ratio are considered together to make

View solution