Transcript ASP.NET - WebForms are the Future, ignore this MVC rubbish

D
E
V
vs
D
B
A
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
who are
you?
Phil Winstanley
Plip
$41T
we add
microsoft expertise
to your development teams
but mostly
we help customers
get their apps built and deployed
and nearly every
application we see
is attached to a database.
so we see
the pain
from the DBA & DEV relationships
EVERYDAY
so,
what’s
the problem?
is
it this?
and,
how
do we fix it?
we’ll
come back
to that…
let’s,
look at
what we hate
about each other.
what
do you
hate about developers?
well?
they dare
to query
your database?
that they
don’t understand
the consequences
of their queries?
that you
can’t tweak
their SQL?
that they think
an empty string
is a null.
perhaps
they blame you
for live application issues?
do you resent that
you are the one
up at 11 PM fixing apps.
when they
are in the
pub?
Oh,
the Schema,
your lovely schema.
the crazy
demands
they place on your schema.
It’s
fair to say
developers are a pain in the…
what
do you
hate about DBA’s?
well,
we love you DBA’s,
really, we do.
but, there are
a couple
of things we don’t like…
we love it,
when we have
no permissions on the database.
although, not quite
as much as when we
almost have enough permissions.
your naming
‘conventions’
drive us insane.
why,
oh why,
are_you_fixated_with_underscores?
oh
and while
we’re on naming ‘conventions’ …
tbl_customers
makes you look
like you need your name
sewn
into your
underpants
by
your
mum
hungarian notation
went out of fashion
about the same time as …
what about,
null values
they’re really hard to work with!
if only
DBA’s knew
the pain
the suffering
the torment
the grief
that
they cause
developers.
well
you do,
we’re in this together.
but
none of this
is the real problem.
and
the real problem
is only going to get worse.
we,
microsoftare one of the main culprits.
say
it isn’t so microsoft,
you’re perfect!
we
can’t seem
to make our minds up.
why have one
data access technology
when you can have …
RecordSets
XML
ADO
ADO.NET
DataSet’s
Adapters
Readers
DAAB
LINQ to SQL
Enterprise Lib
SQLXML
DynamicData
ORM
Entity Framework
and
our new
technology focus?
OData
Oh Dear
like
a massive pile
of chocolates at a party.
ambassador
you’re spoiling us
with data access methods.
but
you’re DBA’s
why should you care?
more, and more
this will become
critical.
sorry DBA’s but
we have control
now.
the time of the
stored procedure
as the only way, is over.
entity framework
and other ORMs
are becoming the standard.
for better
and for worse
they’re here to stay.
legacy systems
won’t change
anytime soon.
but new systems,
they’re a different
story
it’s now
common practice
not to have a database at all.
dah
dah
dah!
gasps
of horror
from the audience.
what’s worse
for DBAs
is we’ll generate the schema...
from the code
after
we’ve built the app.
when it’s
too late
to change anything.
then make it
your problem
forever more.
yeah,
you’re listening now
aren’t you?
so why,
should we fix
this situation?
developers
ask yourselves
this.
how do you
cluster
a database server?
what is the
optimal number
of tempdb files?
what’s a
suspended
session?
and,
do you really
want to know?
no,
you want to build
apps.
DBAs
what do you know
about...
stateless and
statefull
environments?
how best to
optimize
viewstate?
what a
source control
system is?
(just for reference, you
should know that one)
and,
do you really
want to know?
no, you want to
do whatever
it is that DBAs do for fun.
drowning kittens
badger baiting
watching ready steady cook
stuff
like
that.
we
need to fix
this.
now,
before it’stoo late.
so,
how do we fix
this situation?
we need
marriage
guidance.
this isn’t
a technology
problem.
we cannot
fix it with
more technology.
it’s about
the process
we follow…
and
the people
we have…
communication
is key
to this.
right at the beginning
of projects
get together…
talk about how data
will really
be handled
and treat
the whole system
as one
it isn’t
application
and database
it’s a
solution
there is no
one size
fits all.
here are
some tips
to help.
setup
e-mail distributionlists.
get everyone
involved
to sign up.
developers
and DBAs
alike.
and share
in a constructive way
your knowledge.
deliver
quick presentations
on relevant topics
to the
whole team
and discuss them.
don’t be afraid
to pair
program.
test
applications
together.
and please
just talk to
each other
so,
educate
each other.
and,
work
together…
not,
against
one another.
and
developers,
if you can’t get on with your DBA’s
here is something
you can do
to keep them busy.
wait until
just before they’re
going home
open a proc
from a production box
and add this…
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.
there are other sessions
like this one
but suck less
We have many open positions in the
UK
http://careers.microsoft.com/
[email protected]
@plip