October 23, 2008 at 9:01 pm
Comments posted to this topic are about the item Absolutely (Not?)
October 24, 2008 at 12:42 am
I am a developer, who works with databases. I guess DBA's should say absolutely no to:
- Backups;
- Security;
- Hardware.
Visit:
http://www.kaizenlog.com
http://www.autocar-live.com
http://www.yachting-live.com
October 24, 2008 at 1:59 am
I'm with primary keys....
but i'll settle for indexes indexes and more indexes... - developers often assume that what they've written against their dev database which has 50 rows of data will work just as fast with 5000 rows of data.
MVDBA
October 24, 2008 at 2:21 am
michael vessey (10/24/2008)
I'm with primary keys....developers often assume that what they've written against their dev database which has 50 rows of data will work just as fast with 5000 rows of data.
Agree to that.....:)
"Keep Trying"
October 24, 2008 at 2:30 am
I have to put an alternate spin on "indexes, indexes and more indexes" - the developers I work with have the annoying habit of having no clustered index, and using non-clustered indexes on every individual column!
October 24, 2008 at 2:48 am
Infonote (10/24/2008)
...I guess DBA's should say absolutely no to:- Backups;
- Security;
- Hardware.
Actually I think you'll find most DBA's say yes to those! 😉
For my part backups are obviously key and I make sure that I'm involved in the setup of them because otherwise they just wont be done how I want.
But one of my biggest bugbears is security, and people (funnily enough namely consultants from third party software suppliers) using sa as a login to their system. Aaaarrrrrggghhhh! No! No! NO!
October 24, 2008 at 3:17 am
Infonote looks like a spammer/advert re. the sig.
Security,
Security includes backups in my opinion. 🙂
Team work in DB design - Build Test and Tune requires developers and DBAs.
Managers that listen and understand (rare I know but we live in hope) 😉
Hiding under a desk from SSIS Implemenation Work :crazy:
October 24, 2008 at 3:38 am
The only absolute should be that there are no absolutes.... 😉
There should only be guidelines, validation, discussion and feedback.
After a long time in I.T. doing various jobs from Mainframe operations through to development of multi-tier distributed systems one of the things I have observed is that there are always exceptions to every "rule". DBAs, developers, testers, analysts, project managers and business stakeholders should all work together, discuss problems and make sure that each function's (business, dev, test etc.) viewpoint has been considered i.e. look at things holistically - only then can we deliver systems that help our businesses' bottom lines.
Malcolm
DB Ghost - Build, compare and synchronize from source control = Database Change Management for SQL Server
www.dbghost.com
October 24, 2008 at 3:41 am
I, as dba, developer and designer, reject requests that would compromise usability, integrity, security or would unnecessarily complicate GUI, data model or both.
The most recent was like this: two fields from different tables, one is default NULL and is intended as override for the other. "Let it be a copy of the other field, so we don't have to use join and coalesce()". Really? NULL means no override, so with copying you lose relevant info and compromise integrity.
October 24, 2008 at 3:56 am
Shaun McGuile (10/24/2008)
Infonote looks like a spammer/advert re. the sig.Security,
Security includes backups in my opinion. 🙂
Team work in DB design - Build Test and Tune requires developers and DBAs.
Managers that listen and understand (rare I know but we live in hope) 😉
I have removed my signature. I am not a spammer.
Visit:
http://www.kaizenlog.com
http://www.autocar-live.com
http://www.yachting-live.com
October 24, 2008 at 3:58 am
Phil Melling (10/24/2008)
Infonote (10/24/2008)
...I guess DBA's should say absolutely no to:- Backups;
- Security;
- Hardware.
Actually I think you'll find most DBA's say yes to those! 😉
For my part backups are obviously key and I make sure that I'm involved in the setup of them because otherwise they just wont be done how I want.
But one of my biggest bugbears is security, and people (funnily enough namely consultants from third party software suppliers) using sa as a login to their system. Aaaarrrrrggghhhh! No! No! NO!
By absolutely no, I meant they do as developers say. If you are a DBA, and you are convinced that backups as an e.g. are best made daily, you are not going to accept if a developer (or someone else) tells you to make backups weekly.
Visit:
http://www.kaizenlog.com
http://www.autocar-live.com
http://www.yachting-live.com
October 24, 2008 at 3:59 am
Infonote (10/24/2008)
Shaun McGuile (10/24/2008)
Infonote looks like a spammer/advert re. the sig.Security,
Security includes backups in my opinion. 🙂
Team work in DB design - Build Test and Tune requires developers and DBAs.
Managers that listen and understand (rare I know but we live in hope) 😉
I have removed my signature. I am not a spammer.
Good for you dude, welcome to the asylum! 😀
Hiding under a desk from SSIS Implemenation Work :crazy:
October 24, 2008 at 4:01 am
Performance testing code before deploying to production.
I got very tired of devs deploying code to prod without doing any form of performance testing on it. The code frequently performed terribly and then, because it was in production, fixing it was my responsibility
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 24, 2008 at 4:05 am
GilaMonster (10/24/2008)
Performance testing code before deploying to production.I got very tired of devs deploying code to prod without doing any form of performance testing on it. The code frequently performed terribly and then, because it was in production, fixing it was my responsibility
Quote and completely agree! they usually say "So put an index on the table"
Also security is often forgotten: using the same login for all purposes.
My must: backup and check the restore! 😎
See The Jenga blog
October 24, 2008 at 4:08 am
Data Integrity -- imposed early, imposed aggressively. Then I can negotiate with those who want things more relaxed and can justify the request. As opposed to leaving things wide open and then later, when data quality problems are discovered, pleading with people to go back and change processes to treat the data better.
Viewing 15 posts - 1 through 15 (of 92 total)
You must be logged in to reply to this topic. Login to reply