Scribd
Upload
2 views4 pages

ER Model 2

The document discusses the concept of database sessions and privileges in Oracle, emphasizing the importance of managing user access and the dangers of granting excessive privileges. It explains the role of database roles in aggregating privileges for users, the purpose of indexes for performance, and the use of profiles to limit resource usage. Additionally, it highlights the use of triggers to enforce constraints on data, such as limiting student registrations.

Uploaded by

Ai Cha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2 views4 pages

ER Model 2

The document discusses the concept of database sessions and privileges in Oracle, emphasizing the importance of managing user access and the dangers of granting excessive privileges. It explains the role of database roles in aggregating privileges for users, the purpose of indexes for performance, and the use of profiles to limit resource usage. Additionally, it highlights the use of triggers to enforce constraints on data, such as limiting student registrations.

Uploaded by

Ai Cha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

ER Model 2

Question asked by one of the students about the


Role
when you connect with SQLPlus , oracle creates a SESSION , they are not limited
, as soon as you're not disconnected the session , it keeps going , someone with
priviledges can modify your session .
Example : one day , one year .... . you have a space fi la RAM , ki dir disconnect , all
data in the RAM is removed .
To create a Session in the DataBase , you'll need priviledges.
"create seesion to " , I'm giving that user acess bah ykhdem bDB , The DBMS
Allocates space fi la RAM for that user .
Most dangerous priviledge : ALL PRIVILEGE , don't use it at all cases if possible .
Only the system admin and the owner can give the privileges to other users to acess
that object.
To access tables created by the other user , user.tableName .
System Priviledge : what kind of action the user can perform in the DB (craete
session , user , table , index )

DataBase Role : a set of privileges that defines the authority and responsibility of
users assigned to the role.
Really useful to use to implement different bussiness Rules .
Grant chef_service to NewUser --> aggregation of priviliges
Role : in database is predefined . au lieu 3ndk 15 privildges u just use roles and it
is much better.
you can assing a user many roles .
Indexes : extra structure , only for performance
an index y7kem some records yjib address t3hom .
the index is used by the DBMS , not by the user
Profile : Can be used to limit the use of resources By each user .
Triggers ( Personalised Constraint ):
Question asked by a student : how can we assure that each student can be registered
in 3 different max ?

we use Triggers : automaticaly executed to apply some checking on teh 'about to


be inserted' data .

You might also like