rodge
14-07-2008, 18:19
:help: ???????????
|
View Full Version : Name 2 parts of a database? rodge 14-07-2008, 18:19 :help: ??????????? Ghozer 14-07-2008, 18:20 can you give us a little more info? what type of database? what 2 parts? what do you mean? rodge 14-07-2008, 18:21 i just need to know any 2 parts of a data base? Thanks Ghozer 14-07-2008, 18:23 i just need to know any 2 parts of a data base? Thanks Again, what type of database? what 2 parts? what for? when you say 2 parts this could be, 2 tables, 2 columns, 2 pieces of info, or it could be the database + the part to read/write it. Please try and be a little more descriptive rodge 14-07-2008, 18:27 I am just reading it as it says on list of questions i have as part of my collage on enter and find data. List 2 parts of a database? thats all i got The_DADDY 14-07-2008, 18:52 Part 1 and part 2? :D max 14-07-2008, 18:56 Primary and foreign keys. BluePolo 14-07-2008, 19:01 This has to be one of the strangest worded questions I've ever seen on the forum. punk 14-07-2008, 19:03 SELECT wtf, are, you, on, about FROM incomprehensible where IQ<10 and clue=less cgksheff 14-07-2008, 19:25 Various techniques are used to model data structure. Most database systems are built around one particular data model, although it is increasingly common for products to offer support for more than one model. For any one logical model various physical implementations may be possible, and most products will offer the user some level of control in tuning the physical implementation, since the choices that are made have a significant effect on performance. In a hierarchical model, data is organized into an inverted tree-like structure, implying a multiple downward link in each node to describe the nesting, and a sort field to keep the records in a particular order in each same-level list. This structure arranges the various data elements in a hierarchy and helps to establish logical relationships among data elements of multiple files. Each unit in the model is a record which is also known as a node. In such a model, each record on one level can be related to multiple records on the next lower level. A record that has subsidiary records is called a parent and the subsidiary records are called children. Data elements in this model are well suited for one-to-many relationships with other data elements in the database. This model is advantageous when the data elements are inherently hierarchical. The disadvantage is that in order to prepare the database it becomes necessary to identify the requisite groups of files that are to be logically integrated. Hence, a hierarchical data model may not always be flexible enough to accommodate the dynamic needs of an organization. The network model tends to store records with links to other records. Each record in the database can have multiple parents, i.e., the relationships among data elements can have a many to many relationship. Associations are tracked via "pointers". These pointers can be node numbers or disk addresses. Most network databases tend to also include some form of hierarchical model. Databases can be translated from hierarchical model to network and vice versa. The main difference between the network model and hierarchical model is that in a network model, a child can have a number of parents whereas in a hierarchical model, a child can have only one parent. The network model provides greater advantage than the hierarchical model in that promotes greater flexibility and data accessibility, since records at a lower level can be accessed without accessing the records above them. This model is more efficient than hierarchical model, easier to understand and can be applied to many real world problems that require routine transactions. The disadvantages are that: It is a complex process to design and develop a network database; It has to be refined frequently; It requires that the relationships among all the records be defined before development starts, and changes often demand major programming efforts; Operation and maintenance of the network model is expensive and time consuming. Examples of database engines that have network model capabilities are RDM Embedded and RDM Server. Do you see? esme 14-07-2008, 19:34 I'd guess "data" and "structure" as a database has to have some structure to define the relationship between data and it has to have data as it's pretty useless without but thats just a guess and it's probably wrong I am just reading it as it says on list of questions i have as part of my collage on enter and find data. List 2 parts of a database? thats all i got are you seriously making a collage or have you misspelt college ? if it's the former then sorry I don't know anything about art if the latter then what other questions are there on the paper ?, do any of them refer to a specific database ? if they do then maybe thats the database you have to refer to marmite 14-07-2008, 19:44 do you mean like Primary key and all that malarky? fred_notdead 14-07-2008, 19:49 A good site that wikipedia :) http://en.wikipedia.org/wiki/Database Perhaps validation and verification would be another good starting point. . esme 14-07-2008, 20:19 A good site that wikipedia :) http://en.wikipedia.org/wiki/Database Perhaps validation and verification would be another good starting point.. Aw cool, first sentence "A database is a structured collection of records or data" almost word for word what I said, and for my next trick I shall predict next weeks lottery numbers :hihi: adaline 15-07-2008, 09:39 Yeah i think esme hit it on the head in that instance. |