For example, you would not want to recommend fiber channel disks for a system that would be seldom used by few users. Understanding the purpose and the importance of the system will help you determine the best possible configuration and resource requirements. Will it be a configuration database for the corporate anti-virus server?Īre they rolling out a new SharePoint system?.Is this the back-end for a new financial application?.What's required from the database side?.In other words, get some background information first. ![]() Purposeįirst of all, try to understand the system's function and what will it be used for. In the following sections, I will try to list some of the checkpoints DBA can refer to. The DBA needs to take note of those unknown areas, suggest possible solutions or inform and educate his peers. This can range from "we don't know, you tell us" to outright blank stares from around the meeting table. As the DBA asks his questions, not all the answers may be readily available. Having said that, not every project will have an all-encompassing, well rounded set of specifications. That's why it's best to have a list of questions and metrics available at hand. The key thing to do is to understand the purpose of the system and gather as much information as possible. The DBA should also be able to architect the database layer from scratch and be able to support his design. Savvy DBAs should be able to look at a system's design and suggest the best solution for the database tier or recommend any better approach. A lot of brainstorming and whiteboard drawings are happening and people want to know what would be the best configuration for the database server. Management has at last given the green light to an application enhancement project and the project manager has kicked off weekly meetings with developers, architects and DBAs. ![]() You need to suggest what will be the best path for a smooth migration. After months of development, testing and polishing off, the company is ready to take the next big leap as version 2.0 of a core application is ready for rollout.You need to give the final verdict whether the design conforms to good database practices. You have been brought on board at the last moment and asked to review the architecture. The work will begin next week and all the parties have agreed it's a good design. The vendor is doing all the hard work and they have come up with a detailed architecture document. A new, third-party supplied document management system is being implemented in your organization and it's based on.If you think of yourself as an infrastructure DBA, here is a sample of tasks you could be asked to do: He needs to understand what applications are in production, what database back-ends are used, how storage and virtual servers are provisioned, among other things. ![]() Instead, he will have broad knowledge about the enterprise application landscape. They advise developers aboutĬreating re-usable functions or benefits of usingĪn infrastructure DBA on the other hand, may not always have in-depth knowledge of the application. Then validating database object structures. Development DBAs often spend their time reviewing detailed technical specifications, understanding pseudo-code and flow-charts Of the many hats an experienced DBA wears, one is that of a system architect.
0 Comments
Leave a Reply. |