dev

171
D E V D B A vs

Upload: saman

Post on 24-Feb-2016

28 views

Category:

Documents


0 download

DESCRIPTION

DEV. DBA. 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. So. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: DEV

DEVDBA

vs

Page 2: DEV

WHAT YOU’LL LEARN:

• Nothing• Of• Value

Page 3: DEV

READY?

Page 4: DEV

LET’S START BY DISPELLING SOME MYTHS

Page 5: DEV

FIRSTLYDevelopers don’t know jack about databases

Page 6: DEV

SECONDLYDBA’s know nothing about development

Page 7: DEV

THIRDLYThey can each do the others jobs

Page 8: DEV

FINALLYThey can’t work together

Page 9: DEV

you?who areSo

Page 10: DEV

Phil Winstanley

Page 11: DEV

Plip

Page 12: DEV
Page 13: DEV

$41T

Page 14: DEV
Page 15: DEV
Page 16: DEV

to your development teams

microsoft expertisewe add

Page 17: DEV

get their apps built and deployed

we help customersbut mostly

Page 18: DEV
Page 19: DEV

is attached to a database.application we see

and nearly every

Page 20: DEV

from the DBA & DEV relationshipsthe pain

so we see

Page 21: DEV

EVERYDAY

Page 22: DEV
Page 23: DEV
Page 24: DEV

the problem?what’s

so,

Page 25: DEV

this?itis

Page 26: DEV
Page 27: DEV
Page 28: DEV
Page 29: DEV
Page 30: DEV

do we fix it?

howand,

Page 31: DEV

to that…come back

we’ll

Page 32: DEV

what we hatelook at

let’s,

about each other.

Page 33: DEV
Page 34: DEV

hate about developers?

do youwhat

Page 35: DEV

well?

Page 36: DEV

your database?to querythey dare

Page 37: DEV

the consequencesdon’t understand

that they

of their queries?

Page 38: DEV

their SQL?can’t tweak

that you

Page 39: DEV

is a null.an empty string

that they think

Page 40: DEV

for live application issues?

they blame youperhaps

Page 41: DEV

up at 11 PM fixing apps.you are the one

do you resent that

Page 42: DEV

pub?are in the

when they

Page 43: DEV

your lovely schema.

the Schema,Oh,

Page 44: DEV

they place on your schema.

demandsthe crazy

Page 45: DEV

developers are a pain in the…

fair to sayIt’s

Page 46: DEV
Page 47: DEV
Page 48: DEV
Page 49: DEV

hate about DBA’s?do youwhat

Page 50: DEV

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

well,

Page 51: DEV

of things we don’t like…a couple

but, there are

Page 52: DEV

no permissions on the database.

when we havewe love it,

Page 53: DEV

almost have enough permissions.

as much as when wealthough, not quite

Page 54: DEV

drive us insane.‘conventions’

your naming

Page 55: DEV
Page 56: DEV
Page 57: DEV

are_you_fixated_with_underscores?

oh why,why,

Page 58: DEV

we’re on naming ‘conventions’ … and while

oh

Page 59: DEV

like you need your namemakes you look

tbl_customers

Page 60: DEV

underpantsinto your

sewn

Page 61: DEV

mumyour

by

Page 62: DEV

about the same time as …went out of fashion

hungarian notation

Page 63: DEV
Page 64: DEV

they’re really hard to work with!null values

what about,

Page 65: DEV

the painDBA’s knew

if only

Page 66: DEV

the suffering

Page 67: DEV

the torment

Page 68: DEV

the grief

Page 69: DEV

developers.they cause

that

Page 70: DEV

we’re in this together.you do,well

Page 71: DEV

is the real problem.none of thisbut

Page 72: DEV

is only going to get worse.the real problem

and

Page 73: DEV

are one of the main culprits.microsoftwe,

Page 74: DEV
Page 75: DEV

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

say

Page 76: DEV

to make our minds up.can’t seem

we

Page 77: DEV

when you can have …data access technology

why have one

Page 78: DEV

RecordSets

Page 79: DEV

XML

Page 80: DEV

ADO

Page 81: DEV

ADO.NET

Page 82: DEV

DataSet’s

Page 83: DEV

Adapters

Page 84: DEV

Readers

Page 85: DEV

DAAB

Page 86: DEV

LINQ to SQL

Page 87: DEV

Enterprise Lib

Page 88: DEV

SQLXML

Page 89: DEV

DynamicData

Page 90: DEV

ORM

Page 91: DEV

Entity Framework

Page 92: DEV

technology focus?our new

and

Page 93: DEV

OData

Page 94: DEV

Oh Dear

Page 95: DEV

of chocolates at a party.a massive pile

like

Page 96: DEV

with data access methods.you’re spoiling us

ambassador

Page 97: DEV

why should you care?you’re DBA’s

but

Page 98: DEV
Page 99: DEV
Page 100: DEV

critical.this will become

more, and more

Page 101: DEV

now.we have controlsorry DBA’s but

Page 102: DEV

as the only way, is over.stored procedure

the time of the

Page 103: DEV

are becoming the standard.

and other ORMsentity framework

Page 104: DEV

they’re here to stay.and for worsefor better

Page 105: DEV

anytime soon.won’t changelegacy systems

Page 106: DEV

storythey’re a differentbut new systems,

Page 107: DEV

not to have a database at all.

common practiceit’s now

Page 108: DEV

dah!dah

dah

Page 109: DEV

from the audience.of horror

gasps

Page 110: DEV

is we’ll generate the schema...

for DBAswhat’s worse

Page 111: DEV

we’ve built the app.after

from the code

Page 112: DEV

to change anything.too late

when it’s

Page 113: DEV

forever more.your problem

then make it

Page 114: DEV

aren’t you?you’re listening now

yeah,

Page 115: DEV

this situation?should we fix

so why,

Page 116: DEV
Page 117: DEV

this.ask yourselves

developers

Page 118: DEV

a database server?cluster

how do you

Page 119: DEV

of tempdb files?

optimal numberwhat is the

Page 120: DEV

session?suspended

what’s a

Page 121: DEV

want to know?do you really

and,

Page 122: DEV

apps.you want to build

no,

Page 123: DEV

about...what do you know

DBAs

Page 124: DEV

environments?statefull

stateless and

Page 125: DEV

viewstate?optimize

how best to

Page 126: DEV

system is?source control

what a

Page 127: DEV

(just for reference, you should know that one)

Page 128: DEV

want to know?do you really

and,

Page 129: DEV

it is that DBAs do for fun.

do whateverno, you want to

Page 130: DEV

drowning kittens

Page 131: DEV

badger baiting

Page 132: DEV

watching ready steady cook

Page 133: DEV

that.like

stuff

Page 134: DEV

this.need to fixwe

Page 135: DEV

too late.before it’s

now,

Page 136: DEV

this situation?how do we fix

so,

Page 137: DEV

guidance.marriage

we need

Page 138: DEV
Page 139: DEV

problem.a technology

this isn’t

Page 140: DEV

more technology.fix it with

we cannot

Page 141: DEV

we follow…the processit’s about

Page 142: DEV

we have…the peopleand

Page 143: DEV

to this.is key

communication

Page 144: DEV

get together…of projectsright at the beginning

Page 145: DEV

be handledwill reallytalk about how data

Page 146: DEV

as onethe whole system

and treat

Page 147: DEV

and databaseapplication

it isn’t

Page 148: DEV

solutionit’s a

Page 149: DEV

fits all.one size

there is no

Page 150: DEV

to help.some tips

here are

Page 151: DEV

lists.e-mail distribution

setup

Page 152: DEV

to sign up.involved

get everyone

Page 153: DEV

alike.and DBAs

developers

Page 154: DEV

your knowledge.in a constructive way

and share

Page 155: DEV

on relevant topicsquick presentations

deliver

Page 156: DEV

and discuss them.whole teamto the

Page 157: DEV

program.to pair

don’t be afraid

Page 158: DEV

together.applicationstest

Page 159: DEV

each otherjust talk toand please

Page 160: DEV

each other.educate

so,

Page 161: DEV

together…work

and,

Page 162: DEV

one another.against

not,

Page 163: DEV
Page 164: DEV

if you can’t get on with your DBA’s

developers,and

Page 165: DEV

to keep them busy.

you can dohere is something

Page 166: DEV

going homejust before they’re

wait until

Page 167: DEV

and add this…from a production boxopen a proc

Page 168: DEV

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

RETURN;

Page 169: DEV

fin.

Page 170: DEV

but suck lesslike this one

there are other sessions

Page 171: DEV

We have many open positions in the UK

http://careers.microsoft.com/

[email protected]

@plip