Database: Difference between revisions

Revision as of 12:14, 31 October 2013

Revision as of 12:16, 1 November 2013

Line 342:

{{Main|Database tuning}}

After designing a database for an application arrives, the next stage ofis building the database. Typically an appropriate [[general-purpose DBMS]] can be selected to be utilized for this purpose. A DBMS provides the needed [[user interface]]s to be utilized by database administrators to define the needed application's data structures within the DBMS's respective data model. Other user interfaces are used to select needed DBMS parameters (like security related, storage allocation parameters, etc.).

When the database is ready (all its data structures and other needed components are defined) it is typically populated with initial application's data (database initialization, which is typically a distinct project; in many cases using specialized DBMS interfaces that support bulk insertion) before making it operational. In some cases the database becomes operational while empty fromof application's data, and data areis accumulated alongduring its operation.

After completing building the database andis makingcreated, itinitialised operationaland arrivespopulated theit databaseneeds maintenanceto stage:be maintained. Various database parameters may need changeschanging and the database may need to be tuned ([[Database tuning|tuning]]) for better performance,; application's data structures may be changed or added, new related application programs may be written to add to the application's functionality, etc.

Contribution by Malebye Joyce as adapted from informations systems for businesses from chapter 5 - storing ad organizing data. Databases are often confused with spread sheet[[Spreadsheet|spreadsheets]] such as Microsoft excelExcel (Microsoft whichAccess is differenta fromdatabase Microsoftmanagement system, Excel accessis a spreadsheet program). Both can be used to store information, however a database servesis amore betterefficient functionand flexible at thisstoring large amounts of data. Below is a simple comparison of spreadsheets and databases.

{| class="wikitable"

Spread sheets strengths -1. Very simple data storage 2. Relatively easy to use 3. Require less planning Weaknesses- 1. Data integrity problems, include inaccurate,inconsistent and out of date version and out of date data. 2. Formulas could be incorrect Databases strengths 1. Methods for keeping data up to date and consistent 2. Data is of higher quality than data stored in spreadsheets 3. Good for storing and organizing information. Weakness 1. Require more planning and designing

|-

! Spreadsheet strengths !! Spreadsheet Weaknesses

|-

| Very simple data storage || Data integrity problems, including inaccurate, inconsistent and out of date data and formulas.

|-

| Relatively easy to use || Difficult to validate data e.g. an incorrect formula

|-

| Require less planning ||

|}

{| class="wikitable"

|-

! Database strengths !! Database Weaknesses

|-

| Methods for keeping data up to date and consistent || Require more planning and designing

|-

| Data is of higher quality than data stored in spreadsheets || Harder to change structure once database is built

|-

| Good for storing and organizing information. || Requires more technical knowledge to administrate

|}

===Backup and restore===