Re: IBM Consulting info
- From: Guillermo Alan Bort <cicciuxdba@xxxxxxxxx>
- To: ganstadba@xxxxxxxxxxx
- Date: Tue, 14 Jun 2011 13:16:51 -0300
It is both contractual (usually outsourced DBA are just "physical" dbas not
app dbas). I remember all we could do was give the customer the queries we
took from AWR reports order by elapsed time, executions, buffer gets, etc.
We didn't even read them, we just copypasted them (might as well send the
full awr report).
Another contributing factor is that as a way to further reduce costs, they
keep all the teams understaffed, so you end up having to manage way more
databases than you can and you simply don't have the time to get to know the
applications that run in each database.
So I agree that it's a good idea to keep at least one DBA that knows the
environment on the customer side.
Cheers
Alan.-
On Tue, Jun 14, 2011 at 9:02 AM, Michael McMullen <ganstadba@xxxxxxxxxxx>wrote:
> Try to convince your friend to get his company to keep a DBA on as an
> application DBA. My experience with outsourced DBA’s is that they are good
> at the nuts/bolts of being a DBA but not in figuring out what is wrong with
> an application. I think that might be part of the contract but as everyone
> knows, most developers don’t write code to scale. It’s very easy for a DBA
> to say it’s not the database fault, it’s the app. Your company will need
> someone that can zero in on performance problems quickly and identify the
> situation. You won’t get that with IBM.
>
> My best call ever with India was when I had to diagnose a stuck dbwr. That
> part was pretty easy but communicating the problem to India when there was a
> massive dog fight in the background was difficult. I’m not exaggerating, the
> guy said the strays had gotten into the building and were terrorizing the
> place.
>
Other related posts:
