×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

View vs Table???

View vs Table???

View vs Table???

(OP)
Hi,

Can anyone just refresh my memory.

What is the diff. between a View and a Table?

Thanks in advance,

Wilson

RE: View vs Table???

The difference between a table and a view is simple.  A table is the underlying structure that contains the fields, data types and data for the database.  A view is normally a subset of the underlying table in which you restrict the fields and records displayed to the user.  The way to filter these records is usually done by a query or stored procedure based on a table.  Views are an excellent way of keeping the end user from having direct access to the table.  One of the basic rules of database design is that users NEVER have direct access to the underlying data because they can corrupt data!  Views are also a way to implement security.  If you don't want certain users to see certain fields, like a salary field in an employee table, you can restrict them from seeing that information.

RE: View vs Table???

(OP)
Thanks Omega

RE: View vs Table???

Hi Wilson.

The difference between a View and a Table is very simple.  View is an imaginary table which has only a definition and moreover it points to the table only.

Views can be created for a few sets of reasons like

1) Security-> Assume there is a table which has seven fields, whereas you want to enduser to access only three fields then you can create a view to handle this.

Eg : create view <viewname> <Field Names, Field Names,...>
     as Select <required fields> from <Table Name>

this also takes care of even hiding the tablename from the user.

User can be able to update the table only if the other fields which are not part of the view can accept null values.

2) Ease of Use-> Assume a query requires data from more than one table with lots of conditions.  Instead of giving a long select statement, you can create a view to make your life very simple.

View is not going to store any data, it carries only the definiton and points to the base table.

Conditions apply to insert, update or delete a record through a view.

Hope this helps you


Parthi

RE: View vs Table???

(OP)
Thank you very much Parthi.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close