MySQL 5 Administration-Part 1 Tutorials
The Job of the DBA / The Company MySQL Team
Subtitles of the Movie (MySQL 5 Administration-Part 1 / The Job of the DBA / The Company MySQL Team)
As I mentioned in the last lesson, the database administration team in a large organization is not the only team in town that's dealing with MySQL. There's actually a whole eco system of people on the MySQL staff that the database administrators need to interact with. So let's take a look at that and see what the relationships are here. So there are three basic categories of people. Certainly there are database administrators and they're primarily charged with ongoing management of the system as it's running. So the production system and certain amounts of planning and so on that are coming up. There's the database development staff and the application development staff for that matter that has to interface with the database. And their job is to implement those things that the database administrators see are necessary. So you may need to call on them for creating new triggers for tables, for creating events that you want to track something for creating stored procedures and stored functions. All of that kind of stuff would be the job of database development people rather than database administrators who already have their hands full in the first place. Give the developers something to do. And if you're lucky you've also got someone in this third category. Usually only have one or two of these people at the most and that's database architects. So these are people who truly are planning for future growth and trying to help the database administration team and the database developers to come up with fixes to the system as it stands right now. So the architecture not just there for the initial design of the system and then going off forever. They really have an ongoing role to play. Now the important thing about all of this is that these people all need to work together. Too often in companies I see and I'm getting on my soapbox here a little bit. But too often in companies I see these people at war with each other and complaining about each other and grumbling about each other and much of that is because you've got people who are charged with doing database administration who actually were system administrators. And somebody says, well they're administrators so let's just make them the database administrators too. Or you have people who were hired because they were web developers or game developers and now they're also supposed to be doing database development. And believe me there's a totally different mindset for database development than there is for the other things. A true database developer isn't just there to kind of get something to work, however they can get it to work. They want it to work as efficiently as possible because they have the same goal as the database administration team which is to have an efficiently running system. And the same thing for the database architect, not just the person who happens to know the most about programming but somebody who truly has an eye and a mind for design and how all of these things interact. That's what you ideally need to have on this general MySQL team. And I suggest that you start trying to develop that if you don't have that already. Part of that is just going to be training. So teamwork works better than warfare from my point of view. We need to have everybody working toward the same goals and we also need to have everybody involved in the decision making. Not that it's an egalitarian world or anything, managers still have to make decisions. But everybody needs to have input into those decisions because some of those people may understand more than the person on high about specific details and how they're going to be impacted. As a matter of fact and I put a little break here in this slide but even end users have a part to play and need to have some input. The people who are actually using the system, the people who are actually using the applications that we have and do the day to day data entry and querying and so on, they have some important information for you for making the system work better. And as a matter of fact they're going to be more likely to support the system and make it work, rather than find any nit picking little thing to complain about and throw their pens down in disgust and, and not do the job. As long as they have some input, as long as they feel ownership of the system they're going to do everything they can to make it work too and they're going to be one of your best sources of input for how to make things better. So teamwork here is really, really, really important and really everybody who uses the system in some way is on that team, not just the people who are touching the database. So it's always good to be aware of those kind of things. Yes some people will call this politics but it's just humanity. Everybody is there in this company trying to get the job done to make the company succeed so they can get paid. And, and the better everybody works together on this, the more likely that's going to be the outcome and there will be bigger bonuses and all that. Okay. One more little thing then in making this work a little bit better. Let's talk a little bit about hiring practices. We'll do that in the next lesson.
Tutorial Information
| Course: | MySQL 5 Administration-Part 1 |
| Author: | David Swain |
| SKU: | 34307 |
| ISBN: | 978-1-61866-086-2 |
| Release Date: | 2012-12-31 |
| Duration: | 16 hrs / 171 lessons |
| Work Files: |
Yes |
| Captions: | No |
| Compatibility: |
Vista/XP/2000, OS X, Linux QuickTime 7, Flash 8 |
VTC Sign up & Benefits
- Unlimited Access
- 81,350 Video Tutorials (14,200 free)
- Video Available as Flash or QuickTime
- Over 715 Courses
- $30 for One Month Access
- Multi-User Discounts Available
