October 4, 2008 at 5:26 pm
Hello everybody i'am new in Database (sql server) so i need an advice to be a good Database Administrator.
Thanks.
October 4, 2008 at 5:48 pm
I am also a new database administrator. My approach is to focus on the basics at first ... backups, maintenance and the like. Make sure the basic functionality is covered for your databases in a reliable manner and be sure that you understand enough about these functions and your environment so that you can respond in that inevitable crisis situation. Learn the functions and practice them.
October 4, 2008 at 7:40 pm
If you're speaking of what's considered an operational DBA, there are a few basics:
Backup / Restore:
- Understand the backup / restore options SQL Server provides for you.
- Implement those on your databases to meet your users' needs.
- Test those backups regularly to make sure they are good and to give you an idea of how long the restores take.
Configuration / Performance (OS):
- Understand the various types of RAID and how those can impact your performance.
- Understand how to deploy SQL Server on those RAID configurations to meet cost vs. performance.
- Understand how to measure performance on your SQL Servers (CPU, memory, disk I/O).
- Understand what can cause bottlenecks on those areas.
Configuration / Performance (SQL Server):
- Understand clustered vs. non-clustered indexes and what situations to apply them.
- Understand statistics and how to keep them up to date.
- Understand how to determine when indexes are needed and when they're not.
- Understand how to deploy database and log files to maximize the performance of the disk.
Growth / Capacity Planning:
- Understand how to measure the growth of your databases.
- Understand how to forecast growth over time.
- Understand how to communicate your growth needs to management before it's critical.
Security (SQL Server):
- Understand the difference between users/logins
- Understand how to determine what permissions a login has, down into each database.
- Understand ownership chaining.
- Understand how to get a user the rights that are needed, no more and no less.
K. Brian Kelley
@kbriankelley
October 5, 2008 at 8:41 pm
Brian has said it all...very well put :). Of course i will add my .02 from my experience. Make sure you have some broad shoulders and a good knowledge of pretty much EVERY aspect of your system. I am sure that many will agree that when the backups are slow, or applications are running poorly, or networks are running slow, etc... the first stop it appears for EVERY one is the DBA(they will come to you with the problem because data is high on the list). Not only will your prove your data is or is not the problem but your input is quite often wanted for the repair EVEN if its not your field of expertise. Like I was saying Brian is right on the numbers with everything he's quoted..print it and use it as a guideline now and later in your career.
Good Luck
-D-
DHeath
October 6, 2008 at 7:13 am
I'll add one more to the list.
Disaster recovery
- Know how to fix corruption
- Know what to do when someone drops a table (though if you've done the security right, that shouldn't be possible)
- Know how to restore to any point given your backup strategy
- Practice various scenarios so that if something does happen, you know exactly what to do.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 7, 2008 at 7:35 am
Learn to say NO early and often :w00t:
Actually I would say that the main thing is that you understand what is happening in your userbase re:DB access and head off problems before they arrive; even if they are only perception.
October 8, 2008 at 8:59 am
For starters get some good sql server book and read from cover to cover. In my experience this will definitely help as most of the problems that DBAs face are because of ignorance.
October 8, 2008 at 2:36 pm
hi,
can you share all ur experiences for all points u mentioned?
April 24, 2011 at 11:38 am
Hi, I was the SQL Server DBA for two factories running SQL Server in a clustered environment. We had a thruput of 900 transactions per second. Implemented DR and replication using a central distributor. I would agree with all the advice given earlier. So apart for what has been said and stating the obvious read as much as you can on SQL Server - STAY FOCUSED at all times. Don't get lazy. Always be aware of your environment and keep on top of it. A good tool to give you a heads up on potential problems is Spotlight. Hope my input is of use to you going forward. 🙂
April 24, 2011 at 12:00 pm
Please note: 3 year old thread.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply