0% found this document useful (0 votes)
4 views

Dms

Uploaded by

ak.prasad487
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views

Dms

Uploaded by

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

NAME:-PRASAD ANKIT KUMAR VINAY KUMAR

ROLL NO:-242122
COURSE NAME :- CM-Diploma in Computer Technology
ENROLLMENT NUMBER :- 24111610031
SEAT NO:- 135151
Database Administration
• Database administration is the process of managing and
maintaining a database to ensure that it works well, stays secure,
and is available whenever needed
Introduction to database administration:

• Introduction to Database Administration involves overseeing the


entire process of storing, managing, and retrieving data in
databases, ensuring data integrity, security, and availability. Here’s a
brief breakdown:
Types of Database Users

Database
End Users Application System Designers
Programmers Analysts

Database Administrators
(DBAs)
END USER

•Description: End users interact with the database through applications without directly accessing
the database itself.

•Access Level: Limited access, usually restricted to querying and viewing data relevant to their
needs.

•Examples: Employees using a web application to view customer records, clients viewing account
information on a banking app.
Application Programmers

•Description: These are developers who write software applications that interact with the database.
•Access Level: Typically, they have more access than end users, including permissions to create, read,
update, and delete data as needed for application functionality.
•Examples: Programmers developing e-commerce websites, inventory management systems, or other
software that requires data storage and retrieval
Database Administrators (DBAs)

•Description: DBAs are responsible for the overall management, maintenance, and
security of the database. They ensure data integrity, performance, and availability.
•Access Level: Highest level of access, including privileges to manage user
permissions, optimize performance, create backups, and perform recovery.
•Examples: IT professionals managing databases for large organizations, setting
user roles, and implementing security policies.
System Analysts

•Description: System analysts design databases and determine the requirements for database
applications based on organizational needs.
•Access Level: They often have access to define the database schema and determine the structure,
though their direct data manipulation access might be limited.
•Examples: Analysts planning the architecture for data warehouses, setting up data models for
applications.
Database Designers

•Description: These users are responsible for defining the logical and physical structure of the
database. They decide how data will be stored, organized, and related.
•Access Level: Access to design schema, tables, relationships, and indexes but typically less access
to day-to-day data manipulation.
•Examples: Data architects designing a database for a new CRM or ERP system.
User Management

•Create and Delete Users: DBAs can add or remove users


from the database, often setting up initial user accounts and
ensuring they align with company policies.
•Assign Privileges: Using commands like GRANT and
REVOKE, DBAs define access controls, specifying who can
read, write, or modify database information. Privileges can
be fine-tuned to different levels to maintain data security.
Creating and Deleting Database Users
• n most database systems (such as MySQL, PostgreSQL, Oracle, SQL
Server), DBAs can create new users by executing commands that
specify the user's name, authentication method (e.g., password), and
any initial privileges.
EG:-CREATE USER 'username'@'hostname' IDENTIFIED BY 'password’;
In this example:
•'username' is the name of the user.
•'hostname' is the host from which the user can connect (it could be % for
any host or a specific IP address).
•'password' is the authentication password for the user.
Deleting Users

When a user is no longer needed, the database administrator can delete the user to prevent
unauthorized access. This can be done using a simple DROP USER command.
DROP USER 'username'@'hostname’;
Assigning Privileges to Users

Privileges define what actions a user is allowed to perform on the database. These privileges can be
granted at various levels (e.g., global, database, table, or column level) depending on the needs of
the user.
Granting Privileges To grant privileges, you can use the GRANT command. You can assign specific
privileges to users, such as SELECT (read), INSERT (write), UPDATE (modify), DELETE (remove),
and administrative privileges like CREATE, ALTER, and DROP.
GRANT SELECT, INSERT, UPDATE ON database_name.* TO 'username'@'hostname’;

In this example:

SELECT, INSERT, UPDATE are the privileges being granted.


database_name.* means all tables within that database.
'username'@'hostname' is the user being granted the privileges.
2.Revoking Privileges If a user's privileges need to be removed or modified, the REVOKE command is used.
Example (SQL syntax for MySQL):
REVOKE SELECT, INSERT ON database_name.* FROM 'username'@'hostname';
This revokes the SELECT and INSERT privileges from the user.
Best Practices for User and Privilege Management

1. Principle of Least Privilege: Always assign the minimum required


privileges to users to perform their job functions. This helps reduce
security risks.
2. Use Roles: Instead of assigning individual privileges to each user,
consider using roles (which are collections of privileges) to make
management easier and more consistent.
3. Regular Audits: Periodically review user access and privileges to ensure
they are still appropriate and that there are no unauthorized users.
4. Password Management: Ensure users use strong, unique passwords,
and enforce password policies where possible.

You might also like