DEVDEV DBADBA vs

WHAT YOU’LL LEARN: Nothing Of Value

READY?

LET’S START BY DISPELLING SOME MYTHS

FIRSTLY Developers don’t know jack about databases

SECONDLY DBA’s know nothing about development

THIRDLY They can each do the others jobs

FINALLY They can’t work together

you? who are So

Phil Winstanley

Plip

$41T

to your development teams microsoft expertise we add

get their apps built and deployed we help customers but mostly

is attached to a database. application we see and nearly every

from the DBA & DEV relationships the pain so we see

EVERYDAY

the problem? what’s so,

this? it is

do we fix it? how and,

to that… come back we’ll

what we hate look at let’s, about each other.

hate about developers? do you what

well?

your database? to query they dare

the consequences don’t understand that they of their queries?

their SQL? can’t tweak that you

is a null. an empty string that they think

for live application issues? they blame you perhaps

up at 11 PM fixing apps. you are the one do you resent that

pub? are in the when they

your lovely schema. the Schema, Oh,

they place on your schema. demands the crazy

developers are a pain in the… fair to say It’s

hate about DBA’s? do you what

really, we do. we love you DBA’s, well,

of things we don’t like… a couple but, there are

no permissions on the database. when we have we love it,

almost have enough permissions. as much as when we although, not quite

drive us insane. ‘conventions’ your naming

are_you_fixated_with_underscores? oh why, why,

we’re on naming ‘conventions’ … and while oh

like you need your name makes you look tbl_customers

underpants into your sewn

mum your by

about the same time as … went out of fashion hungarian notation

they’re really hard to work with! null values what about,

the pain DBA’s knew if only

the suffering

the torment

the grief

developers. they cause that

we’re in this together. you do, well

is the real problem. none of this but

is only going to get worse. the real problem and

are one of the main culprits. microsoft we,

you’re perfect! it isn’t so microsoft, say

to make our minds up. can’t seem we

when you can have … data access technology why have one

RecordSets

XML

ADO

ADO.NET

DataSet’s

Adapters

Readers

DAAB

LINQ to SQL

Enterprise Lib

SQLXML

DynamicData

ORM

Entity Framework

technology focus? our new and

OData

Oh Dear

of chocolates at a party. a massive pile like

with data access methods. you’re spoiling us ambassador

why should you care? you’re DBA’s but

critical. this will become more, and more

now. we have control sorry DBA’s but

as the only way, is over. stored procedure the time of the

are becoming the standard. and other ORMs entity framework

they’re here to stay. and for worse for better

anytime soon. won’t change legacy systems

story they’re a different but new systems,

not to have a database at all. common practice it’s now

dah! dah

from the audience. of horror gasps

is we’ll generate the schema... for DBAs what’s worse

we’ve built the app. after from the code

to change anything. too late when it’s

forever more. your problem then make it

aren’t you? you’re listening now yeah,

this situation? should we fix so why,

this. ask yourselves developers

a database server? cluster how do you

of tempdb files? optimal number what is the

session? suspended what’s a

want to know? do you really and,

apps. you want to build no,

about... what do you know DBAs

environments? statefull stateless and

viewstate? optimize how best to

system is? source control what a

(just for reference, you should know that one)

want to know? do you really and,

it is that DBAs do for fun. do whatever no, you want to

drowning kittens

badger baiting

watching ready steady cook

that. like stuff

this. need to fix we

too late. before it’s now,

this situation? how do we fix so,

guidance. marriage we need

problem. a technology this isn’t

more technology. fix it with we cannot

we follow… the process it’s about

we have… the people and

to this. is key communication

get together… of projects right at the beginning

be handled will really talk about how data

as one the whole system and treat

and database application it isn’t

solution it’s a

fits all. one size there is no

to help. some tips here are

lists. distribution setup

to sign up. involved get everyone

alike. and DBAs developers

your knowledge. in a constructive way and share

on relevant topics quick presentations deliver

and discuss them. whole team to the

program. to pair don’t be afraid

together. applications test

each other just talk to and please

each other. educate so,

together… work and,

one another. against not,

if you can’t get on with your DBA’s developers, and

to keep them busy. you can do here is something

going home just before they’re wait until

and add this… from a production box open a proc

RAISERROR ('Transaction (Process ID 53) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction', 16, 1 ); RETURN;

fin.

but suck less like this one there are other sessions

We have many open positions in the UK