what do you mean by ELT responsibility of DBA
Answers
Answer:
Mark Mine As the Brainliest
Explanation:
Responsibilities of a database administrator differ from company to company.
There are several kinds of DBA's - the main ones are
- Infrastructure DBA (more focus on storage, servers, resources / not that much focus on the actual data and logic which is developers responsibility)
- DBA/Developer (developing & testing new code, keeping database available, fixing code bugs, tuning performance of the applicaiton)
- Apps DBA (DBA with overlap into the Application server/Middleware area extending the responsibility of a DBA for application layer)
In large companies these roles can become even more granular or come in different shapes and sizes.
Regardless what platforms are you administering you will be responsible for these things:
Backup/Recovery - Every database administrator is ultimately responsible for making sure he can bring the data back if something bad happens.
Life brings all kinds of scenarios that you have to deal with, under stress, with managers breathing up your neck asking "is it up yet?". At those times DBA must stay cool and focused, regardless of a mind burden that operation/survival of entire company may depend on him at that moment.
Security - Great emphasis should be put on keeping the data safe, making sure only those people who need access have it, making sure you have adequate password policy, making sure you scramble sensitive data when cloning, making sure to audit sensitive data,makings sure all known security bugs are addressed.
As a DBA you have to have strong personal integrity and resist all temptations to look at the data you have at hand, whether those are CC numbers, SSN, Salary information, medical records etc.
Performance - Database engine main advantage is that it let's you to ask relatively complex questions over a big pile of data and get you a response very quickly. As a DBA you have to ensure that the response times for queries are according to user expectations. There are countless techniques of performance tuning and countless unique scenarios that you will need to analyze. Many performance problems stretch across layers, so as a DBA it is good if you have skills to troubleshoot these layers (network, OS, application etc.). You can dedicate your entire career to performance tuning and you will constantly learn something new.
Problem resolution - This is usually DBA's daily bread. There is always something that can go wrong (and goes wrong), the more complex system the more likely something will slip through the cracks even in the most rigorous change/release management practice. These days you can find "how to" for just about every problem you may encounter on the internet. The responsibility of a DBA is to understand which "solutions" are real for your situation and how to mitigate risk that comes hand in hand with any of these "solutions" that you find on the internet.
Periodic maintenance - Keeping your database supported and as bug free as possible requires patching, upgrades, applying bug fixes, workarounds, tweaks etc. Keeping track of what was applied where, with what result is also typically part of the DBA job. Database is alive and likes to grow and mature, so you will be moving things around, migrating to different platforms, exporting, importing data, reclaiming space etc.
Monitoring - Being informed at the time when things are happening is invaluable. Not only that it looks more professional when you reply to manager who escalates the problem "We know about this and we are already working on a solution".
Some problems are very difficult to be troubleshooted once they are gone, so monitoring the right things to keep you in the know of what is going on with your database is also essential and can help you to prevent even bigger problems.
Capacity planning - Data is always growing, so you need to make sure you can cope with the growth and resource demands. As a DBA you will be asked how much storage we will need next year? Will the current server cope with the roll out of this new feature for 1000 users? etc. You have to be prepared to be able to answer these questions and more.
So, as a DBA you should do all of the above and more if you decide to do so. Reality is, most likely you will not have time to do all of the above unless you are exceptionally experienced, disciplined and structured.