September 7, 2010 at 10:34 am
Hi,
Most importantly, try to learn the business as much as possible, this will earn you respect from your peers.
Also being able to play datacop and defend your DB Design is another important point you should adhere to as a DBA.
Thanks,
Amol Naik
January 14, 2014 at 11:09 am
Change Management.
Disaster recovery plan if the company has any?
List of DB which are problematic.
Planned maintenance window.
Who is responsible for applying patches?
Security policies.
Backup policies. How long your company keep the data.
Ticket/Escalation process?
"He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]
January 14, 2014 at 11:34 am
Note that this is a thread over 3 years old.
However, it's nice that you try to help 😉
January 14, 2014 at 4:09 pm
Lol.
Thanks guys.
Just for your information.
After I posted this; I ended up doing more of MS BI work and less of DBA work even though I got a job as a DBA
and as a result of that I became a very good SSRS/SSIS developer.
A really good one with 6-7 years of experience who is getting paid more than our company's senior DBA :).
$$$ matters who cares about title as long as I stay with DB,right?
Viewing 4 posts - 31 through 33 (of 33 total)
You must be logged in to reply to this topic. Login to reply