Ideal data dictionary, Database Management System

An ideal data dictionary should have everything a DBA wants to know about the database.

1 Conceptual, External, and internal database descriptions.

2.    Descriptions of attributes (fields), entities (record types) as well as origin, cross- references and meaning of data elements.

3. Authorisation ,Synonyms and security codes.

4. Which external schemas are used by which programs, what their authorisations are, and who the users are.

5.  Statistics about database and its usage containing number of records, etc.

A data dictionary is executed as a database so that users can query its contents. The cost efficiency of a data dictionary increases as the difficulty of an information system increases. A data dictionary can be an enormous asset not only to the DBA for database design, execution and maintenance, but also to managers or end users in their project planning.

Posted Date: 3/6/2013 5:02:41 AM | Location : United States







Related Discussions:- Ideal data dictionary, Assignment Help, Ask Question on Ideal data dictionary, Get Answer, Expert's Help, Ideal data dictionary Discussions

Write discussion on Ideal data dictionary
Your posts are moderated
Related Questions


The result of the UNION operation between R1 and R2 is a relation that includes? The result of the operation between R1 and R2 includes all the tuples of R1 and R2 which have c

does tables are called relations

Differance between procedural and non procedural DML? Procedural and non procedural DML Procedural DML exactly what data is require and how to obtain those data. Non procedural

DISADVANTAGES OF RDBMS

give some example real-life situations where DBMS are most suiitabe

There are three main sources of utilities and applications for a DBMS: a. Vendor applications and utilities are given for working with or maintaining the database, and generally

what is RDBMS? how it works? good example.

What is conceptual schema? The schemas at the view level are known as subschema that describe dissimilar views of the database.