Become a star DBA
Want to become the best DBA around?
Here's our quick guide to help DBAs quickly and easily be at the top of their game. By following these quick tips, you'll take control of your database environment and reduce the overall potential for crises to occur.
Contents
- Tip 1: Make an inventory
- Tip 2: Standardise configurations
- Tip 3: Create a customised maintenance plan
- Tip 4: Ensure the security of your system
- Tip 5: Get on good terms with your developers
- Tip 6: Develop a comprehensive disaster recovery strategy
- Tip 7: Take and test regular backups
- Tip 8: Monitor and maintain performance
- Tip 9: Know where to find information
Tip 1: Make an inventory
As a DBA, you'll usually have servers to manage, from perhaps just a couple to maybe a thousand or more; we recommend that you spend some of your time understanding what servers you have within your environment and some very basic information about them. We recommend that as a minimum, you grab the following information:
- Machine name, manufacturer, and model.
- Memory size.
- Number of CPUs.
- CPU speed (maximum clock speed).
- Disk size (are they raided?)
- Networks card (how many, what speed?)
- Battery backup available?
- OS (name and version).
Tip 2: Standardise configurations
As systems grow or as different DBAs stamp their authority and own working practices on their servers, you could find that configurations are different on them. When standardising server configurations, consider the role of each server in your organisation.
Tip 3: Create a customised maintenance plan
Server maintenance is crucial to the performance of the business and is usually the domain of either a network administrator or sometimes the DBA. If this does fall within your remit then having a formal, customised plan will help you.
We don't want to worry you too much but without a proper maintenance plan, the application software is likely to not run as it is expected and in very severe cases, the network can even experience partial or total failure leading to severe losses to your business.
So in order to keep the business' computer and server network in a reliable condition, you'll need to ensure that your servers are checked and updated on a regular basis and that the installation of patches is routinely completed.
You're probably best getting the network team (server experts) to undertake the work, but someone will need to ensure that the tasks are routinely checked and completed. Make that your task.
Tip 4: Ensure the security of your system
We seem to be always hearing about high-profile hacking attacks that continue to prove that web security remains one of the biggest issues facing any IT team today. If any external facing servers are your responsibility then you need to get to grips with this, this is especially true if you are looking after web servers as they are one of the most targeted public faces of an organisation.
Tip 5: Get on good terms with your developers
Developers and DBAs (along with network personnel) need to work closely together, spending more time together discussing application performance.
This also stops any future finger pointing, which hampers the company's abilities to produce the very best performance.
Patience, information sharing, and collaboration can lead to much larger and more comprehensive performance improvements.
Tip 6: Develop a comprehensive disaster recovery strategy
It goes without saying that if things go wrong (as they sometimes do) then you need to be able to leap into action and resolve issues quickly with a limited amount of downtime.
The key step here is to list all of your critical systems and the threats to these systems.
Tip 7: Take and test regular backups
As part of your disaster recovery plan, I'm sure that creating backups of your data is included.
At a minimum, your backup set should consist of:
- The last backup of the control file and all data files
- All archived redo logs generated from when the last backup was taken
- Configuration files such as
odbc.ini
,tnsnames.ora
,listener.ora
, and so on.
The frequency of your backups is based on a number of factors; if users generate a significant amount of data changes then you'll have more frequent backups. Also, if you make any changes to databases or systems then you really should make backups before you start.
If your database is mainly read-only, and if updates are issued only infrequently, then you can probably get away with backing up the database less frequently.
Tip 8: Monitor and maintain performance
Keeping a constant eye on your server performance is possibly one of the most important responsibilities of your role.
Modern server monitoring tools will provide you with an easy way to maintain a good vigilant approach as they can provide you with real-time alerts, and report functionality can keep you up to date with any potential problems.
Tip 9: Know where to find information
You're going to know your own role fairly well, but do you know who to contact or where your corporate information is held?
Not only do you know have to know the who, what, and where internally, but DBAs are expected to constantly keep up with the rapidly-changing technology. Have you signed up for the news channels from your database vendors and signed up for the relevant groups, forums and blogs around the internet?
Thank you.
This has been a quick look at the important tips that we think will give you a good head start in your DBA role. The role of a DBA can be a stressful and rewarding one. Enjoy it, and remember if we can be of any assistance in your data access tasks, just get in touch.