Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
What is an Admin DBAs Role 3
- Thread starter lilsamp
- Start date
-
2
- #2
This is from a section of the book .... Microsoft SQL Server DBA Survival Guide
DBA Responsibilities
The following sections examine some of the responsibility of the database administrator and how they translate to various Microsoft SQL Server tasks.
Installing and Upgrading a SQL Server
The DBA is responsible for installing SQL Server or upgrading an existing SQL Server. In the case of upgrading SQL Server, the DBA is responsible for making sure that, if the upgrade is not successful, the SQL Server can be rolled back to an earlier release until the upgrade issues can be resolved.
Monitoring the Database Servers Health and Tuning Accordingly
Monitoring the health of the database server means making sure that the following is done:
The server is running with optimal performance.
The server is properly configured with the correct amount of memory and the proper configuration parameters.
The error log or event log is monitored for database errors.
Databases have routine maintenance performed on them and the overall system has periodic maintenance performed by the system administrator.
Using Storage Properly
Maintaining the proper use of storage means making sure that databases and transaction logs are created correctly, monitoring space requirements, and adding new storage space when required.
Performing Backup and Recovery Duties
Backup and recovery are the DBA's most critical tasks; they include the following aspects:
Establishing standards and schedules for database backups
Developing recovery procedures for each database
Making sure that the backup schedules meet the recovery requirements
Managing Database Users and Security
The DBA is responsible for setting up user's database server login IDs and determining the proper security level for each user. Within each database, the DBA is responsible for assigning permissions to the various database objects such as tables, views, and stored procedures.
Working with Developers
It is important for the DBA to work closely with development teams to assist in overall database design, such as creating normalized databases, helping developers tune queries, assign proper indexes, and aiding them in creating triggers and stored procedures.
--------------------------------------------------------------------------------
TIP: I have too often seen DBAs who were content to sit back and watch developers make bad design and SQL Server decisions. I have also seen situations in which the DBA wanted to be involved in design decisions but management prevented it because it was not the DBA's "job." Don't be underutilized. If you are in this situation, show your management this tip! Take an active role in new project development. The entire team will benefit from your insight and knowledge!
--------------------------------------------------------------------------------
Establishing and Enforcing Standards
The DBA should establish naming conventions and standards for the SQL Server and databases and make sure that everyone sticks to them.
Transferring Data
The DBA is responsible for importing and exporting data to and from the SQL Server. In the current trend to downsize and combine client/server systems with mainframe systems, importing data from the mainframe to the SQL Server is a common occurrence.
Replicating Data
SQL Server version 6.x has added a new requirement and responsibility for the DBA: setting up and maintaining data replication throughout the workplace. Replication is a tremendous feature that will play a big part in many organizations.
Scheduling Events
The database administrator is responsible for setting up and scheduling various events using Windows NT and SQL Server to aid in performing many tasks such as backups and replication.
Providing 24-Hour Access
Although you may say to yourself, "No way!," the database server must stay up and the databases must always be protected and online. Be prepared to perform some maintenance features and upgrades after hours. If the database server should go down, be ready to get the server up and running. After all, that's your job.
Learning Constantly
To be a good DBA, you must continue to study and practice your mission-critical procedures, such as testing your backups by recovering to a test database. In this business, things change very fast so you must continue learning about SQL Server, available client/servers, and database design tools. It is a never-ending process.
Thanks
J. Kusch
DBA Responsibilities
The following sections examine some of the responsibility of the database administrator and how they translate to various Microsoft SQL Server tasks.
Installing and Upgrading a SQL Server
The DBA is responsible for installing SQL Server or upgrading an existing SQL Server. In the case of upgrading SQL Server, the DBA is responsible for making sure that, if the upgrade is not successful, the SQL Server can be rolled back to an earlier release until the upgrade issues can be resolved.
Monitoring the Database Servers Health and Tuning Accordingly
Monitoring the health of the database server means making sure that the following is done:
The server is running with optimal performance.
The server is properly configured with the correct amount of memory and the proper configuration parameters.
The error log or event log is monitored for database errors.
Databases have routine maintenance performed on them and the overall system has periodic maintenance performed by the system administrator.
Using Storage Properly
Maintaining the proper use of storage means making sure that databases and transaction logs are created correctly, monitoring space requirements, and adding new storage space when required.
Performing Backup and Recovery Duties
Backup and recovery are the DBA's most critical tasks; they include the following aspects:
Establishing standards and schedules for database backups
Developing recovery procedures for each database
Making sure that the backup schedules meet the recovery requirements
Managing Database Users and Security
The DBA is responsible for setting up user's database server login IDs and determining the proper security level for each user. Within each database, the DBA is responsible for assigning permissions to the various database objects such as tables, views, and stored procedures.
Working with Developers
It is important for the DBA to work closely with development teams to assist in overall database design, such as creating normalized databases, helping developers tune queries, assign proper indexes, and aiding them in creating triggers and stored procedures.
--------------------------------------------------------------------------------
TIP: I have too often seen DBAs who were content to sit back and watch developers make bad design and SQL Server decisions. I have also seen situations in which the DBA wanted to be involved in design decisions but management prevented it because it was not the DBA's "job." Don't be underutilized. If you are in this situation, show your management this tip! Take an active role in new project development. The entire team will benefit from your insight and knowledge!
--------------------------------------------------------------------------------
Establishing and Enforcing Standards
The DBA should establish naming conventions and standards for the SQL Server and databases and make sure that everyone sticks to them.
Transferring Data
The DBA is responsible for importing and exporting data to and from the SQL Server. In the current trend to downsize and combine client/server systems with mainframe systems, importing data from the mainframe to the SQL Server is a common occurrence.
Replicating Data
SQL Server version 6.x has added a new requirement and responsibility for the DBA: setting up and maintaining data replication throughout the workplace. Replication is a tremendous feature that will play a big part in many organizations.
Scheduling Events
The database administrator is responsible for setting up and scheduling various events using Windows NT and SQL Server to aid in performing many tasks such as backups and replication.
Providing 24-Hour Access
Although you may say to yourself, "No way!," the database server must stay up and the databases must always be protected and online. Be prepared to perform some maintenance features and upgrades after hours. If the database server should go down, be ready to get the server up and running. After all, that's your job.
Learning Constantly
To be a good DBA, you must continue to study and practice your mission-critical procedures, such as testing your backups by recovering to a test database. In this business, things change very fast so you must continue learning about SQL Server, available client/servers, and database design tools. It is a never-ending process.
Thanks
J. Kusch
-
1
- #3
#1 Job for a DBA - Keep the database up and available
You'll be tuning the performance of the database(s), you will be administering LOGINS and other security functions, checking that scripts run properly, creating jobs and scheduling them, doing maintenance (backups, defragging, reindexing, etc).
But as I said, the #1 most important job is to keep the database(s) up and making sure the data is available to the users.
-SQLBill
You'll be tuning the performance of the database(s), you will be administering LOGINS and other security functions, checking that scripts run properly, creating jobs and scheduling them, doing maintenance (backups, defragging, reindexing, etc).
But as I said, the #1 most important job is to keep the database(s) up and making sure the data is available to the users.
-SQLBill
- Thread starter
- #6
<sarcasm>
1) Be the first one to know there is a problem after hours (i.e., there is a problem at 2:32am -- and you are expected to be there by 2:35am to fix it).
2) Be the last one to know there is a problem during business hours (i.e., it's been creating random data for the last four hours... did you need to know that?)
</sarcasm>
1) Be the first one to know there is a problem after hours (i.e., there is a problem at 2:32am -- and you are expected to be there by 2:35am to fix it).
2) Be the last one to know there is a problem during business hours (i.e., it's been creating random data for the last four hours... did you need to know that?)
</sarcasm>
nigelrivett
IS-IT--Management
>> #1 Job for a DBA - Keep the database up and available
Think it's to ensure that the system is recoverable.
i.e. if the m/c is lost that it can be restored to the point agreed.
Secondary is to ensure that the system is available.
Of course it can be agreed that the system can be rebuilt from scratch which makes the primary task simple - if the task is ignored then this is implicit. If backups aren't tested then this is implying the same approach.
I see a lot of systems where backups either aren't taken or not tested - i.e. implying that the business doesn't mind losing all the data.
======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Think it's to ensure that the system is recoverable.
i.e. if the m/c is lost that it can be restored to the point agreed.
Secondary is to ensure that the system is available.
Of course it can be agreed that the system can be rebuilt from scratch which makes the primary task simple - if the task is ignored then this is implicit. If backups aren't tested then this is implying the same approach.
I see a lot of systems where backups either aren't taken or not tested - i.e. implying that the business doesn't mind losing all the data.
======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question