Skip to Main Content

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, sasanka.

Asked: November 13, 2017 - 8:27 pm UTC

Last updated: December 08, 2017 - 6:30 am UTC

Version: Exadata

Viewed 1000+ times

You Asked

First of all why people or do not understand or u people force .
DBA primary role and still they r rude ( back up , recovery ,upgrade, monitoring ) a system. It is the most crucial part as Data Loss , recovery can not not be priced. It is a 24*7 job and still fall short.
Similarly for specific application DB architects can teach DBAs for performance & design any day any time .

Exadata needs B tree indexes ,DB Design . Without Indexes when i looking for data profile , data correction it will be max to max storage index,projection for 2-3 rows. highly inefficient .

With CLOUD the biggest fraud with respect to design

Except security guards , , in premise infrastructure , mirrored backup ina real production environment will u cut down ADMIN ppl ?

Similarly illiterate Hadoop Guys think Design and admin goes hand in hand .
Please come out . Self driving Cars , is a piss but Early warning system is a boon .


and Connor said...

I answered a question about hiring DBA's a couple of days ago.

https://asktom.oracle.com/pls/apex/asktom.search?tag=how-to-hire-a-lead-oracle-dba

I said the most important thing, the thing that shows that a DBA will be a real asset to the company is:

"their ability to communicate at all levels"

I think that's probably all I need to say.

Rating

  (2 ratings)

Is this answer out of date? If it is, please let us know via a Comment

Comments

My question was different and my fault i was not succint . Let me put the question ina simple way

sasanka ghosh, November 14, 2017 - 3:11 pm UTC

My concern is that people are confused between DBA and DB Architect role .
As per my understanding there r some overlapping area like Performance tuning , deciding on storage, DB level parameter etc. but after that their role are mutually exclusive i.e.
Do not think DBAs will have time left for Logical model , Physical model , data mapping , writing business logic after their daily work of Backup, recovery, monitoring , upgrade security, applying changes to DB etc and similarly Db designer also will not have time left after doing mapping , requirement analysis , , data mapping , ETL rule, Data flow rule for application etc .

In short Admin and Design Architecture have some overlapping area but most r mutually exclusive i.e. NEEDS DEDICATED RESOURCE and specialized skill set.

With Hadoop etc. i feel people r getting confused .

Recently i had 1-2 experience where very senior level guys in large ORGs also thinking in that way and i feel they r underestimating both the Roles.
Do u agree ?



Connor McDonald
December 01, 2017 - 2:58 am UTC

I think role separation is becoming a thing of the past.

(I'm not necessarily saying that is a *good* thing, but I think it where we are heading).

People aren't looking for someone who can do performance tuning, and backup/recovery. They are looking for people who can *automate* as much of the job as they can, and free up their time to get closer to *business* functions rather than technical functions.

So they become not just database specialists, but *data* specialists - they do modelling, they do integration, they know app servers, they know a myriad of data storage technologies.

That's the future (in my opinion)

A reader, December 07, 2017 - 8:42 pm UTC

When you post a question , can you not refrain from using "IM" style words ( or letters ) ?

How long does it anyone to type "You" in place of "U"?

I miss Tom in this case . He would have reinforced these basic professional communication skills .
Connor McDonald
December 08, 2017 - 6:30 am UTC

As I said in the initial response:


"their ability to communicate at all levels"

I think that's probably all I need to say.