DBAs- What is your biggest pet peeve with developers?
-
Hello, I am working on a presentation on how developers could improve their relationship with their dbas. I am trying to receive as much feedback as possible. What is the biggest pet peeve(s) DBAs have with developers?
-
Hello, I am working on a presentation on how developers could improve their relationship with their dbas. I am trying to receive as much feedback as possible. What is the biggest pet peeve(s) DBAs have with developers?
And you are asking this in a developer forum! You might be better served trying SQL Server Central and the Oracle forums, you are going to get a higher DBA content there. Personally I think we (developers) need to understand the restrictions under which a good DBA works.
Never underestimate the power of human stupidity RAH
-
Hello, I am working on a presentation on how developers could improve their relationship with their dbas. I am trying to receive as much feedback as possible. What is the biggest pet peeve(s) DBAs have with developers?
-
Hello, I am working on a presentation on how developers could improve their relationship with their dbas. I am trying to receive as much feedback as possible. What is the biggest pet peeve(s) DBAs have with developers?
Member 13200024 wrote:
What is the biggest pet peeve(s) DBAs have with developers?
I don't know but I have never understood why there are problems. It really boils down to egos. A lot of people in this industry have too big of an ego and can't work well with other people. I've been lucky enough to never work for such a big company that there were different roles like that. I've been lucky enough to always be a dba and a developer. I have heard stories where developers do not have enough access to the DB so it makes it hard to do their job when they are always waiting on some dba to write code for them. But I'm not sure what complaints the dbas have about devs.
Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
-
Hello, I am working on a presentation on how developers could improve their relationship with their dbas. I am trying to receive as much feedback as possible. What is the biggest pet peeve(s) DBAs have with developers?
This is a little late, but here go some of my annoyances. 1) The sky is falling emails. Just because your application isn't working, doesn't mean the entire environment is down. 2) CCing everyone in management because you are having an issue... 3) Failure to plan, just because you failed to plan out a release doesn't constitute an emergency on my part. Not communicating releases and complaining when something doesn't work right. [The DW team, loves to chew up 100s of gigs of space in a single release without communicating then screaming about when the drives fill up] 4) Trying to use the Database server as a File server, send mail server, or other random stuff. No, the database server is there to serve up data, not be some Swiss utility knife. 5) Not keeping in mind my time, and the totality of the environment. Please start out with where your problem is at. I have 1700 databases spread across Dev, Test, PreProd and Production. No I don't just know where you are having an issue at, if I was psychic I would come up with the winning lotto numbers so I no longer need to work. 6) Security rules are not just setup randomly, they are often established by controls put in place by auditors. I am accountable to those rules, so everyone needs to follow them. Things like demanding SA rights to a db instance, no, there is nothing at the Database Server level you need to change. Things have been setup that way for a reason. 7) Not taking advice on a designs that are just terrible. Just because it worked with 10 rows of data doesn't mean it will scale with 10M rows. Complaining about the server isn't going to solve your issue. Setting aside the petty grips, a lot of the issues boil down to communication and a willingness to collaborate. My time gets stretched in a lot of directions, I go from meetings with network, server, dev, auditors, management, vendors and yes even end users. It’s not always possible for me to just drop everything to help someone out.
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.