Bad database design,
development and implementation is an all too common experience of many a
DBA and Developer alike. In the first session Mark Broadbent will first
demonstrate why pessimistic concurrency is not the problem. Lastly we
have two of the leading experts in TDD who have come all the way from
America to present on how and why TDD should be used to prevent bad SQL
code and defects in your Database.
18:00-18:30 Registration, Refreshments and food
The Warm Up
18:30-19:00 READPAST & Furious: In defence of being Pessimistic - Mark Broadbent
One of the biggest criticisms about SQL Server used to be that fact
that (unlike some of it's rivals) it uses pessimistic concurrency as its
default isolation level and so started the dreaded use of the NOLOCK
hint. SQL Server 2005 introduced the optimistic concurrency
implementation of READCOMMITTED isolation and if that wasn't enough for
the critics, a brand new optimistic isolation level was also introduced.
Well, even to this day, the use of NOLOCK and READUNCOMMITTED is
rife, along with a new problem -the over-use of optimistic concurrency
isolation to avoid blocking issues.
Perhaps we are looking at this all wrong? ...Lets find out.
Speaker Bio can be found at http://tenbulls.co.uk/about/
The Main Event
19:15-20:45 TDD – Thwarting Database Defects - Sebastian Meine & Dennis LLoyd
It’s bad enough to spend hours finding and fixing database defects,
explaining to the rest of the team what went wrong and trying to clean
up the mess. It’s even worse when a defect causes the end-user to make a
bad decision. Database defects are far too costly and most testing
practices do not adequately detect or prevent them. This presentation
introduces tSQLt, a framework for automated database unit testing.
You’ll learn techniques to write SQL code that is resilient to defects
and is easier to change and maintain.
Speaker Bios can be found at http://sqlity.net/en/about/ and http://www.testdrivendatabases.com/
20:45-21:00 Wrap up and Close