Linked by Eugenia Loli-Queru on Mon 10th Oct 2005 01:07 UTC
Is your IT team conducting an internal feud, with team members struggling against each other instead of fighting the real problems of limited time, money, and manpower to support your organization's technology needs? Buck Woody argues that you can't afford to become the Hatfields and McCoys. Also, both developers and DBAs have merit in the IT team. Although different, both jobs are crucial for a successful enterprise. However, conflicting responsibilities sometimes trigger members of the two related professions to face off. Baya Pavliashvili points out a few common situations that can cause tension between the two groups and provides some advice for working your way out of an argument before it leads to a war.
Thread beginning with comment 42455
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:Isn't this the DBAs job, to make sure that the database schema is kept clean?
This is why if there must be a DBA they must to be part of the DEVELOPMENT team and go to the development meetings, etc. Let IT do backups and restore. It is THE reason that you are having trouble with _those_ developers. Your organization does not know which side of the fence you should be on.
Most DBAs discover, though, that there is more power and money in claiming databases and whining about developers. It is way too common.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
Why bother to understand a schema. Just add fields and tables as you desire. Why bother to think about the long term usability of the schema when adding this field here and that field there and this table here and that table there will make the code work today.
Geeze the db runs slow. instead of figuring out the problems, lets create a table but only have a subset of the data so the query goes fast. Then lets create 3 or 4 duplications of the data throughout the database so that when Bob's query runs we get one result set and when Janes runs we get another. Then what the f*ck is the DBA doing that we have such wierd results.
Geeze I cannot put this crap data into these fields, I'll just drop the foreign keys and now it works. One bug fixed.
Views indexes, we don't need no stinkin' performance and nomalization.
mark mcginnis