What is the difference between Table and Relation in Database?

Answer 1

In a table each column attributes are independent, In a table row order & column order are mandatory & that cannot be changed, Table can be of more than 2 dimentions, There may be of rows and columns duplication in a table. Relation: In a Relation in which all attributes are dependent in one or the other way, The row and column orders are not considered, Relation is always 2 dimentional, There cannot be duplication of rows and columns in a relation There is no difference they both refers to the collection of rows and colls which used to store data.

_________________________________________________________

Table The physical instantiation of a relation in the database schema. Relation A logical construct that organizes data into rows and columns.

A table is essentially a two-dimensional matrix. But, a relation need not be so.

Answer 2

Table

In a table each column attributes are independent,

In a table row order & column order are mandatory & that cannot be changed,

Table can be of more than 2 dimentions,

There may be of rows and columns duplication in a table.

Relation

In a Relation in which all attributes are dependent in one or the other way,

The row and column orders are not considered,

Relation is always 2 dimentional,

There cannot be duplication of rows and columns in a relation

Answer 3

A table holds data, in fields (columns) and entries (rows). In relational DBMSes, table-to-table relations play a major role in how data (and tables by extension) are connected to each other.

For example, you have two tables named "Transactions" and "Clients". The "Clients" table contains the clients' names, client ID number, and their contact information. The "Transactions" table contains a list of transactions, ordered by transaction ID and transaction date. The relation here is the client ID number, which MUST be unique in the "Client" table (because you can't have two people sharing the same ID), but not unique in the "Transactions" table (a client can make multiple transactions).

Through this table-to-table relationship, if some employee decides to help a client look up their transaction history, the employee can search by the client ID, or if the client knows the transaction ID (which can be printed on a receipt, invoice, or some other documentation), the information about both the transaction and/or the client will be referenced.