Database Programming

Database is a collection of interrelated data. One entry in a database is referred as one record.

Micro Processor is the main processing unit of the computer. It is call Central Processing Unit. If pins are broken, it will not work.

Cylinder-head-sector, also known as CHS, was an early method for giving addresses to each physical block of data on a hard disk drive. In the case of floppy drives, for which the same diskette medium can be low-level formatted to different capacities, this is still true. Although CHS values no longer have a direct physical relationship to the data stored on disks, pseudo CHS values (which can be translated by disk electronics or software) are still being used by many utility programs

There is many publications that has related literature on information systems. This type of literature can be found online, in libraries, or in textbooks.

For which trigger timing can you reference the NEW and OLD qualifiers?

about $8,000 per month

Computerised databases are made on the computer like library and paper based databases are made by hand or computer then printed off like a catalogue. and computerised data is quicker

CL3 the lower the value the better

Microsoft's world headquarters are in Redmond, Washington, USA. Microsoft has jurisdiction in many other states. Their office locations can be found on their website at: http://www.microsoft.com/about/companyinformation/usaoffices/ .

Pro: It is readable by default in both Linux and Windows operating systems

Con: 4 GB file limit. Fragments badly on larger drive

use FAT32 for something like a jump drive, use ext3 with a windows driver or NTFS on main hard drive

HOW MANY TYPES OF DATABASES IN COMPUTERS PLS GIVE ME LIST OF IT. 4

to track patients and their contact details

In file processing system a permanent system file is created for every new object. Application softwares are used to manipulate these files. SO characteristics (Some of them became its drawbacks) of file processing system are:-

1)Data redundancy and inconsistency

2)Difficulty in accessing data

3)Data isolation ie. data is in different formats and files.

In database system these issues where addressed, by data abstraction.

In DBMS, data is stored using 3 levels of abstraction

1)Physical Level : How data is stored

2)Conceptual level : What data is stored, relationship between data

3)View Level : What is visible to different users.

No. If you've just taken one of the top of a stack its just a protector. Makes a great coffee cup stand though

Normalisation means make table very effective and usable means make table atomic ,unique primary key,not redundancy etc.

ENHANCED ENTITY RELATIONSHIP OR EXTENDED ENTITY RELATIONSHIP

The insert will error due to the field definition of "number".

Data is inserted into a database. Users need to get information from the database. These requests are called "queries". Data is continually being inserted into the tables in the database. There is a utility called "update statistics" which gathers information from the table and feeds is to the "query optimizer". The query optimizer, based on information gathered from update statistics, chooses the most efficient path to gather the data for the user and return the results as quickly as possible. How often statistics must be updated is completely dependent upon the frequency and quantity of updates/inserts/deletes into the table. If the table is static (unchanged), then once update stats is ran, there is no need to run it again.

Backup files should be kept in a different location [CD, thumb drive, external drive] in case your computer breaks down. If the hard drive fails or the operating system crashes, you have your files safe somewhere.

1) Database is designed and built with data for a specific purpose.

2) We can perform the operations simply on database.

3) Database provides a logical relational b/w its record and data.

An Entity merely represents something you want to keep a list of. Two lists can exist that have a relationship with each other - for example Student (a list) enrols in (a relationship) Course (a list). Of course a student can enrol in many courses and a course can have many students enroled in it. Therefore the relationship between Student to Course is "many to many". Many to many relationships between entitities in a relational database management system are resolved by placing a third entity between the entities involved. In ER diagrams this is noted by drawing a box around the relationship diamond - thus promoting the relationship to an "associative entity". The cardinality of the two orignial entities ("many to many") is removed. New cardinality ("one to many") between the outer entities (Student and Course) and the associative entity (Student.Course) with the many towards the associative entity. The data in the associative entity - from the above example - tells us which student is enrolled in which course. (In the following illustration, please ignore underscores. They just space the words out. "{" and "}" denote many) : Entity_____Associative Entity____Entity : STUDENT -------{STUDENT.COURSE }----COURSE : Fred_________ Fred.Math__________ Math : Sally_________ Fred.Science________Science : Gus__________Gus.Math___________Cooking : _____________Gus.Cooking : _____________Sally.Math : In a real database the values recorded in the STUDENT.COURSE table would not be student names and course titles. They would be the primary key values from the STUDENT and COURSE tables. The benefits of this design are:

1) The student is only recorded once which helps minimise data errors.

2) The course is only recorded once which helps minimise data errors.

3) Students can enrol in many courses and courses can have many students enrolledd.

In 1679

a collection of data is supplied by the database vendor. example: Oracle