What Am I?
I really appreciated what Stephen was asking in our last edition of the SSWUG Newsletter when he raised the question “What do we call ourselves?” His referencing the same phenomenon I entitled the changing role of the DBA. I think Steve got it right. The problem is not the different titles that can be made out of the acronym DBA; Database Analyst; Database Architect; Database Administrator.
The problem appears to be more in the Title, skills and responsibilities of individuals working directly with the database systems. Perhaps if we break them down by Skills and Responsibilities, titles may emerge. There used to be a very clear distinction of skills, roles and responsibilities. That distinction has changed in some shops, and become more rigid in others.
Perhaps that would be the best place to start. Why not write in with the kinds of people you hire to work with your databases in any fashion? Specify, as concisely as you may, what skills are required, and what responsibilities the role bears. If you have a title that may be nice to know as well.
Send your thoughts and comments to btaylor@sswug.org. If we get enough response we may be able to pick something out of the noise.
Cheers,
Ben
$$SWYNK$$
Featured Article(s)
Planning for ETL
This article discusses about how to prepare data transfer and staging solutions. I also talked about how to determine the sources and destinations of data and how to identify extract and load the windows that are available to the sources and destinations. At last l discussed about how to evaluate the source data and identify inconsistencies and anomalies in the data.
Featured White Paper(s)
Go Beyond SCOM Monitoring with Foglight for SQL Server
read more)