You are on page 1of 4

Features

Objects; tables
In a database, a table is a set of data elements or values, that are in a model of
vertical columns, and horizontal rows, and a cell name is referred to the point
where the column and row intersect, for example column B and row 24, the cell
name would be B24. A table can have any number of rows, but only a specified
number of columns.

Queries
A query is the name given to a request for data results, for action on data or
both. Queries can be used to answer questions, do calculations, combine data, or
to add, remove/delete data from other tables in the database.

Forms
A form is a database object that can be used to design a user interface for a
database application. A bound form is a form that is directly connected or
binded to a data source, such as a table or query, and can be used to both
enter and edit data, as well as displaying data.
Reports
A report in a database is the result of formatted database queries, and these
contain a lot of information that could prove useful to decision making and
analysis. Most business applications contain a build in reporting tool and this is
simply a front end interface that calls or runs back end database queries that are
formatted for easy application use.

Naming conventions;

The AdventureWorks sample uses a very clear and consistent naming convention
that uses schema names for the organization of database objects.

1. Singular names for tables

2. Singular names for columns

3. Schema name for tables prefix (E.g.: SchemeName, TableName)

4. Pascal casing (a.k.a. upper camel case)

Primary and foreign keys;


A primary key can be defined by the keys shown in the screenshot below. There
can sometimes be two or more primary keys, for example the PartJob table has
two primary keys, and these are called composite primary keys. A foreign key is
a primary key that has been used in another table, example here would be the
customer and job table, in the customer table Customer ID is a primary key, but
in the job table its appeared again but without the key beside it, however it is
the many link in a one to many relationship between the two tables.

Relationships;
There are two types of relationship in a database, one to many, one to one and
many to many etc.
A relational database is that with a collection of data items organized as a set of
formally described tables from which data can then be reassembled/repurposed
without having to reorganise the tables. One to one; this type of relationship
only allows on record on each side of the relationship. The primary key relates to
only one record, or none of the records in the other tables. For example in a
marriage, each spouse has only one other spouse. This relationship can be
applied to a single table, and therefore does not use a foreign key. One to
many; a one to many relationship allows a single record in one table to connect
to multiple records in other tables. For example a single customer can make
multiple orders, but one order can belong to only one customer. Many to many;
this is a complex relationship in which many records in a table can link to many
records in another table. For example, a business probably needs not only
Customers and Orders tables, but likely also needs a Products table. The
relationship between the Customers and Orders table is one-to-many, but
consider the relationship between the Orders and Products table.
Data types;
Short text
Number
Dates/Time
Long text
Currency
Composite primary key
Auto number
Yes/No tickbox
OLE Object
Hyperlink
Attachment
Calculated
Field Properties;
Field name
Field size
Format
Input mask
Default value
Validation rule