What is your definition of DBA?
by Ben Kubicek
Today we have a guest editor Steve is on a trip to England.
I know the simple answer is the database administrator, but what is this role? What would you say if you had to describe it to a non-technical person? DBAs can have many different roles and functions. Some of the roles or features I've seen/done are: Install SQL Server, manage server performance, including disk space utilization, manage backups, control access and permissions/roles for users, manage replication and always-on/multiple failover clusters and performance tuning/indexing, SQL jobs, alerts, Database Mail , the published DB script. I think these can be called core DBA responsibilities.
I also see that some DBAs have some extra responsibility depending on the size of the company you're working on. May be described as more database developers, such as proc that create tables, views, functions, and storage. Or more in the field of data architecture, such as database design, schemas, normalization of tables, keys, and indexes. Sometimes, the DBA may manage the SSIS package, which enters and/or extracts data from the database. Sometimes, they may need to use SSRS or other reporting tools to do some reporting. When you move to a bi environment, you may have data warehouses and ETL packages to manage. I'm sure there are other things I've missed as a DBA.
In my previous work, I was hired as a. NET developers, as well as database development. It's a very small store, and I'm a store with the most database experience. Before I knew it, I was installing SQL Server, setting up backup and managing SQL Server performance, and so on. I spent 9 years in that job, and about two-thirds of the work was done by DBAs, database architects, or database developers, either for the company I work for or for their clients. No one really wants me to do it, I just jump in when I see the need.
Now some people are aiming at a minimum in their work. They just want to stay under the radar. These people, when they are DBAs, may be doing enough work. The database server is running, and so on, but this is not the DBA I want to define. I think there is one thing that can define a good dba, a person who is willing and willing to jump on and beyond their job description. They are managing their core responsibilities, but are willing to help in other areas mentioned above, which may be considered DBA work. They are not afraid to learn/try new things. They are the team players who want to see a successful project, they are willing to roll up their sleeves and stain their hands in the process.
How do you define a DBA? What is your current job description?
Translation: What is your definition of DBA?