Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


The Abstract DBA


The Abstract DBA

Author
Message
Andy Warren
Andy Warren
SSCrazy Eights
SSCrazy Eights (9.5K reputation)SSCrazy Eights (9.5K reputation)SSCrazy Eights (9.5K reputation)SSCrazy Eights (9.5K reputation)SSCrazy Eights (9.5K reputation)SSCrazy Eights (9.5K reputation)SSCrazy Eights (9.5K reputation)SSCrazy Eights (9.5K reputation)

Group: Moderators
Points: 9505 Visits: 2728
Comments posted to this topic are about the item The Abstract DBA

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
David.Poole
David.Poole
SSCertifiable
SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)

Group: General Forum Members
Points: 6043 Visits: 3237
I became a DBA because I needed those skills to do what I wanted to do with data.

I enjoy all aspects of database development and in particular get a buzz out of building a system that manages to make a complex task simple.

I have to say that service packing and hardware management aren't a point of interest.
Dev/Ops is an interesting exception.

As I've moved up to a Data Architect role I've had to relinquish permissions and that has hurt. The reality is that my role requires me to have a higher level view of systems and data flows so I can specify systems that balance many concerns and interests rather than focus exclusively on the needs of one particular group....... But I miss the development aspect, I really, really miss it.

LinkedIn Profile

Newbie on www.simple-talk.com
john.riley-1111039
john.riley-1111039
SSC Journeyman
SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)

Group: General Forum Members
Points: 91 Visits: 204
I have been in I.T. for over 30 years now, and what you describe in your article is an example of a general trend that I have observed over time, and that is that roles are becoming narrower and more specialised.

In the early days, I.T. people tended to be generalists who knew a bit about most things, and would learn what they needed to get a job done. It was quite easy to move from one role to another, and employers did not demand a list of very specific skills as long as your arm before they would even interview you.

Now, although there are a lot more people employed in I.T. it is much more difficult to move roles because employers want you to have experience in all the tools, apps and techniques they are using. You can be rejected because your experience of a given product is not on the version of it that they are using, even though your domain knowledge of their business area is strong. (This has happened to me.)

Another downside to the role-narrowing trend is that people have less understanding of the roles and processes that interact with their own work. That can lead to decisions being made where the impact of that decision on dependent or related processes is not considered.

So whilst it does mean you can focus on one particular thing, it is bad for future employment prospects, and can have an impact on harmonious working.
TomThomson
TomThomson
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: General Forum Members
Points: 12927 Visits: 12158
I was in IT for over 40 years, and remained a pretty much a generalist throughout.

I think overspecialisation has caused problems in our industry; probably a fairly high ratio of specialists to generalists makes sense when some small fields are very complex, but in general employers and recruiters take it too far with the sort of detrimental (and silly) effects mentioned by John Riley.

I think being just a DBA is something that would have driven me bats.

Tom

lshanahan
lshanahan
Mr or Mrs. 500
Mr or Mrs. 500 (500 reputation)Mr or Mrs. 500 (500 reputation)Mr or Mrs. 500 (500 reputation)Mr or Mrs. 500 (500 reputation)Mr or Mrs. 500 (500 reputation)Mr or Mrs. 500 (500 reputation)Mr or Mrs. 500 (500 reputation)Mr or Mrs. 500 (500 reputation)

Group: General Forum Members
Points: 500 Visits: 436
I agree with John, the IT field (considered as a whole) has specialized and while it makes moving into new roles more difficult, having more positions available for narrower roles would create opportunities at least theoretically. That's a debate we could go round and round on all day.

What is interesting even with the specialization of IT, there is still a tendency in the business world to think of IT folks in the old 'generalist' mindset. If you do something with IT, you are assumed to automatically know everything there is to know not only about computers, but virtually every other electronic gadget out there as well. People all the time ask me about smartphones and the like and I look at them and say, "my cell phone makes phone calls." They look at me weird and then the light turns on. It's actually kind of fun in a way.

I haven't been in the database part of IT long enough to know for sure, but from over here in the cheap seats of the peanut gallery, I can't help but think the rise of data science and "big data" will bring even more specialization within the database field itself. Something to think about anyway.

____________
Just my $0.02 from over here in the cheap seats of the peanut gallery - please adjust for inflation and/or your local currency.
harendra 12972
harendra 12972
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 23
I don't agree with system team, a DBA role shall not be narrowed to just instance of sql server,I think both the teams work together to get best out of the box. If someone thinks that DBA should have limited access as low as DBA can't make the system down, it mean's you shoudn't expact from that DBA can do much. I am assumesing that the DBA is not just a development DBA or Application DBA.
Gary Varga
Gary Varga
SSChampion
SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)

Group: General Forum Members
Points: 13637 Visits: 6464
I am a developer and have never been a DBS. That I have known more about RDBMS than some DBAs does not say much about me (I am NOT claiming to be that good) but has more to say about some DBAs. As far as SQL Server is concerned, I have preferred the times when I have been writing an application and the DBA has stated that stored procedures written by programmers will be treated as a specification i.e. they will rewrite as they feel necessary. Sometimes that has been an ego boost when a stored procedure has needed no changes following review whilst other times I have been totally schooled.

I don't mind learning and have a reasonable understanding of my limitations so I couldn't go wrong.

So how does this fit in with the editorial? I am happy for others to specialise in what I may sometimes have done (or do) as a peripheral task of my role. There is more than enough to know without worrying about someone doing some of what used to be part of my ever expanding role.

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (71K reputation)SSC Guru (71K reputation)SSC Guru (71K reputation)SSC Guru (71K reputation)SSC Guru (71K reputation)SSC Guru (71K reputation)SSC Guru (71K reputation)SSC Guru (71K reputation)

Group: General Forum Members
Points: 71590 Visits: 40747
Although I absolutely love the idea of not having to tend the hardware or Windows anymore, I'm still very aware of both and the things that can go wrong as well as the problems having to do with security. In that vein, nothing will convince me to use the Cloud because I don't know the people who are tending to that whereas I do know the people in my company. And, yes... I still know how to make the necessary changes in an emergency where I'd have to wait for some person in the Cloud to decide to work on my help-desk ticket request.

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Andre Ranieri
Andre Ranieri
Mr or Mrs. 500
Mr or Mrs. 500 (531 reputation)Mr or Mrs. 500 (531 reputation)Mr or Mrs. 500 (531 reputation)Mr or Mrs. 500 (531 reputation)Mr or Mrs. 500 (531 reputation)Mr or Mrs. 500 (531 reputation)Mr or Mrs. 500 (531 reputation)Mr or Mrs. 500 (531 reputation)

Group: General Forum Members
Points: 531 Visits: 379
I started as an IT generalist before gradually migrating to a development role then SQL data specialist and DBA. I still have a keen interest in storage and systems configurations to support the SQL Server infrastructure, but am happy to relinquish the daily sysops chores such as routine service pack patching, etc, to focus more on SQL tasks like planning and testing disaster recovery, performance tuning, scalability and such.

Andre Ranieri
Eric M Russell
Eric M Russell
SSCrazy Eights
SSCrazy Eights (9.7K reputation)SSCrazy Eights (9.7K reputation)SSCrazy Eights (9.7K reputation)SSCrazy Eights (9.7K reputation)SSCrazy Eights (9.7K reputation)SSCrazy Eights (9.7K reputation)SSCrazy Eights (9.7K reputation)SSCrazy Eights (9.7K reputation)

Group: General Forum Members
Points: 9721 Visits: 10359
In a large organization, database administrator (DBO) should be a different role from system administrator (SYSADMIN). There are plenty of roles where a DBA basically just needs to be the DBO on a specific databases, he built it and he maintains it, but he doesn't administer the server itself, especially in a case where multiple project teams share a single instance.


"The universe is complicated and for the most part beyond your control, but your life is only as complicated as you choose it to be."
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search