Agile Database Techniques and over 2 million other books are available for Amazon Kindle . Learn more
  • RRP: £26.99
  • You Save: £4.05 (15%)
FREE Delivery in the UK.
Only 2 left in stock (more on the way).
Dispatched from and sold by Amazon.
Gift-wrap available.
Agile Database Techniques has been added to your Basket
Trade in your item
Get a £1.02
Gift Card.
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See this image

Agile Database Techniques Paperback – 17 Oct 2003

See all 3 formats and editions Hide other formats and editions
Amazon Price New from Used from
Kindle Edition
"Please retry"
"Please retry"
£12.84 £2.24

Trade In this Item for up to £1.02
Trade in Agile Database Techniques for an Amazon Gift Card of up to £1.02, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Learn more

Product details

  • Paperback: 480 pages
  • Publisher: John Wiley & Sons; 1 edition (17 Oct. 2003)
  • Language: English
  • ISBN-10: 0471202835
  • ISBN-13: 978-0471202837
  • Product Dimensions: 18.5 x 2.5 x 23.6 cm
  • Average Customer Review: 3.0 out of 5 stars  See all reviews (3 customer reviews)
  • Amazon Bestsellers Rank: 547,241 in Books (See Top 100 in Books)
  • See Complete Table of Contents

More About the Author

Discover books, learn about writers, and more.

Product Description

From the Back Cover

"I wish I had a book like this eight years ago. You’ll want to be sure to have enough copies for both your development and database folks." —Jon Kern, Founding Member of the Agile Alliance "You will find workable, real–world advice here." —Doug Barry, Author, Web Services and Service–Oriented Architectures and The Object Database Handbook An agile database administrator (DBA) has the difficult task of focusing on data–oriented issues, including traditional database administration as well as any application development involving data. Agile DBAs also collaborate with enterprise professionals to ensure that the efforts of the project team reflect enterprise realities. Scott Ambler has written this invaluable book from the point of view of an agile DBA, enabling you to learn the techniques that agile DBAs use to work effectively on evolutionary (iterative and incremental) software projects. With every chapter you’ll be introduced to essential facets of data–oriented activities such as: The basics of object orientation, relational databases, data modeling, and how to deal with legacy data issues Database refactoring, an evolutionary technique that enables you to improve your database design in small steps Mapping objects to relational databases, performance tuning, database encapsulation, and supporting tools Implementation techniques and strategies such as concurrency control, security access control, finding objects in relational databases, referential integrity, and the effective use of XML Strategies and advice for individuals who want to become agile software developers and organizations that want to adopt agile techniques

About the Author

SCOTT AMBLER is president and a senior consultant of Ronin International (www.ronin–, a software services consulting firm that specializes in software process mentoring and object/component–based software architecture and development. He is a contributing editor for Software Development magazine and a columnist for Computing Canada. His personal Web site is

Inside This Book (Learn More)
First Sentence
Since the early 1990s, I've been working with both object and relational database (RDB) technologies to build business applications, and since the mid-1990s I've done a fair bit of writing on the subject. Read the first page
Explore More
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Search inside this book:

Customer Reviews

3.0 out of 5 stars
5 star
4 star
3 star
2 star
1 star
See all 3 customer reviews
Share your thoughts with other customers

Most Helpful Customer Reviews

3 of 3 people found the following review helpful By Thing with a hook on 11 Jan. 2007
Format: Paperback
This is very well written, enjoyable book, with few (if any) competitors. Given its agile sensitivities, it's perfect for a programmer looking for an overview of the whole data modelling she-bang, from use cases to impedance mismatch. Despite clocking in at 400 pages of fairly dense type, interspersed with various tables and UML diagrams, it's a breeze to read. It assumes a bit of knowledge of database technologies, but you don't need anything more than a nodding familiarity with SQL and basic concepts like normalisation.

This book deals with a lot of issues related to using databases as part of agile modelling. The main message is that agile application developers need to think about persistence issues, and database admins need to understand agile development. The differences between data-driven and object-driven models are clearly laid out, and there's an excellent section on refactoring databases.

The important thing about this book is not so much offering you specific solutions to problems, but alerting you to potential problems you might not even know exist, and explaining that you do have options in solving them. As well as introducing agile methods like TDD and refactoring, it also covers database issues like transactions, security, concurrency and object-relational mapping.

Additionally, there is an emphasis on the organisational and political issues you might face in transitioning to agile methodologies, and it's very pragmatic in pointing out that some things that might be considered the preserve of an application developer, could be done in the database itself. The issues are presented at the same level of detail as those presented in the likes of The Pragmatic Programmer (but a different subject, of course).
Read more ›
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
1 of 1 people found the following review helpful By Mr. Si Smith on 23 Nov. 2009
Format: Paperback
I purchased the book looking for guidance on how to apply agile techniques to the database environment.

The books covers a very broad range of subject right from the concepts of normal form to UML etc as covered by the other review.

What it doesn't do is talk about, TDD with regards to the database in the level of depth I expected (in fact there is little coverage of this area). I found this suprising given that more and more TDD is being adopted not just for languages like Java and C#, but also now that Microsoft Team Suite is including this into it's product.

Having said that the books is comprehensive in terms of it's coverage of database theory and it was an excellent refresher and would recommend the book for someone looking for a broad coverage of the database within companies.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
By F. Gil on 12 Aug. 2010
Format: Paperback Verified Purchase
I'm profoundly dissapointed by the book. I know it was written in 2002 and technology has moved since but I just feelt like going back to university where everything is mostly theory.
There's no single real-life example of anything. Just text, text and text.
Annoyingly there are occasions in which a UML diagram that is explained in 3 steps and to make his point he doesn't stick to the original example.

Although there are a few interesting sections I'm sorry to say that was almost a total waste of time for me.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again

Most Helpful Customer Reviews on (beta) 14 reviews
37 of 37 people found the following review helpful
Good material, but too fragmented for my taste 23 Jan. 2004
By Lasse Koskela - Published on
Format: Paperback
Agile Database Techniques is a brilliant book. Already after reading the first chapter I felt like I had been run over by a truck, wondering why I haven't paid more attention to these issues before. Yet, it also has its flaws which I will go into further down.
Ambler starts laying out the groundwork for the second part of the book by introducing his Agile Data method, UML and data modeling. He also gives a very useful jump-start tutorial on data and class normalization and discusses the infamous object-relational impedance mismatch. Worth noting is that in each chapter (throughout the book) Ambler makes sure that the reader understands how the subjects relate to the role of an agile DBA and what should he be looking out for. The subjects in part one were introduced so well that I more than once thought, "I've never seen such a well-balanced and informative tutorial."
The second part of the book focuses a bit on how evolutionary software development is the reality and how techniques such as Agile Model-Driven Development and TDD can assist in surviving in this climate. The chapter on database refactoring is intriguing and the more comprehensive list of database refactorings, found in the appendices, is something I'll definitely Xerox and keep with me in my traveling tool bag. The second part also covers database encapsulation strategies and approaches to mapping objects to relational databases which, again, is a delightfully comprehensive tutorial, as well as touching on the topic of performance tuning.
The third part is a seemingly random collection of subjects such as finding objects in a relational database, referential integrity, concurrency, security, reports and XML with databases. The text is again of high quality and provides an entertaining walk through the woods, but I feel that these chapters had very little to contribute to the subject of the book. This disconnect is made even more clear when Ambler finishes with a 10-page guide on how to become agile and to introduce agility into the organization.
After reading the book, I feel confused. On the other hand, this book is full of little islands of useful insights that I wouldn't think twice recommending for others to read. On the other, the book as a whole is very fragmented and pretty far from what the book's title might suggest. If you pick up the book with an open mind like I did, you'll gain plenty. Otherwise, you'll probably be disappointed to find out that one half of the book probably talks about something you weren't expecting based on the title. After a long struggle, I'm giving this book "only" fours stars despite that it contains some very, very high quality material.
19 of 21 people found the following review helpful
Plenty of dog-eared pages... 3 Feb. 2004
By "agilecoder" - Published on
Format: Paperback
"Agile Database Techniques" is aptly subtitled "Effective Strategies for the Agile Software Developer". Take special note of the word "strategies", because what you will not find within is pages of code and implementation details. This is not a bad thing as there is so much ground to cover that getting caught up in the low-level details of how to implement a particular strategy in language (add yours here) would have limited the scope of the book. Instead, what you will find is a detailed set of skills and development methodologies required by the developer who finds him or herself immersed in the details of modeling, implementing, and/or refactoring the database schema for their current application.
Should you buy this book? Well, try answering the following questions:
- Could you easily create a physical data model of your schema?
- Can you explain the difference between first and third normal form?
- What about first and third object normalization forms?
- Can you list the challenges in mapping an object model to a data model?
Did you answer honestly? Because these are just some of the items covered in Part One of the book and unless you said yes to all of the above, you will walk away with plenty of ideas for improving your development after a single reading. This is the core reason I would recommend this book. It is full of ideas that you might never have thought to include in your development practices, and probably some that you had thought about but were not sure what the best approach might be.
My complaint with "Agile Database Techniques" is that it could use another iteration. In the introduction, the author states "When I first started writing this book, I intended its focus to be on the agile data method... Because I was taking an iterative and incremental approach to the development of the book, I quickly realized that the real value lay in detailed development techniques instead of yet another methodology." While I can agree with and embrace the merits of applying agility to my development practices, I think there is an overabundance of methodology content in the book that only clouds its real value.
In summary, I think this is one of those books that will sit on my shelf for some time to come as a great reference for how to approach any number of application and database development related items.
14 of 17 people found the following review helpful
If this was a novel they'd be bidding for the movie rights 22 Oct. 2003
By A Customer - Published on
Format: Paperback
This is the best book I've bought in years. It starts with an overview of agile software development, something that every single IT professional needs to understand these days. It also overviews basic skills such as data modeling, object modeling, and normalization. Ambler is absolutely dead on with this material: everyone needs to understand the basics of both object development and database development if they're going to get the job done. I'm really surprised how few object and data books actually deal with these basics, they always seem to focus on only one part of the overall picture. Why hasn't someone written just this section before?????
More importantly the book has chapters on agile model driven development and test driven development, two topics that are critical to your success as an agile programmer. Anyone doing XP needs to be up to speed on both these techniques. in particular TDD but just as importantly AMDD.
A really cool chapter talks about database refactoring, which is basically refactoring for relational databases. Anyone who wants to be an effective DBA needs to learn this stuff. There's also an appendix with a catalog of DB refactorings. This material alone is worth the price of the book.
I didn't think that the chapters on basic programming issues such as concurrency control, referential integrity, database access, and reporting would be of interest. Man was I wrong. Ambler takes what I thought were dry subjects and shows how many implementation choices you actually have. I can't remember how many arguments I've gotten into with DBAs, or programmers, who thought there was only one way to do these things. Most importantly he discusses the tradeoffs of each strategy and tells you when they work best. If you're designing a new application this material is critical.
If you're struggling to find ways for programmers and DBAs to work together effectively you really need this book. It shows how to overcome the "people impedance mismatch" that you see in most companies. DBAs need to work in agile ways, and this book tells how to do exactly this.
7 of 8 people found the following review helpful
OK, but not much from a DBA side of things 27 Sept. 2007
By martin dreis - Published on
Format: Paperback Verified Purchase
To be fair, the book title suggests that it is for the software developer, and not a database administrator. I thought that it had a good overview of agile related items. Although it was probably not as useful for software developers who might have more exposure to the agile methods. From a DBA point of view, I thought it was a nice overview because agile is not typically used in DBA teams.

As far as specifics relating to databases, I thought it could have had more real-life scenarios and suggestions on how to deal with them. Some of the ideas presented were just too unrealistic for my liking.

That being said, there are a few good ideas in this book. It was a quick read too. So if you are a DBA who has no idea of agile, it might be something to start with.
9 of 11 people found the following review helpful
A book for all seasons--and programmers and DBAs 17 Dec. 2003
By Gary K. Evans - Published on
Format: Paperback
Scott Ambler is uniquely qualified to write this book. He started his software life as a data modeler, and is now an industry thought-leader in agile, object-oriented software development practices. He wrote Agile Database Techniques to address a single issue that he is obviously passionate about: is it possible for data professionals to develop their data in an evolutionary way? Ambler answers this question with a resounding "yes"! And his book is a manifesto on how the data and object communities can lay down their weapons and join forces to create better software.
Part One addresses the basics of agile development, database concepts and data normalization, object concepts and object normalization ¯- which may be a new concept to some readers. If you are not a data person, you will get a good introduction to the data world-view. If you are not an object person, you will gain insight into why object people see the world from a behavioral view, not the data-centric view. What I found appealing was Ambler's willingness to leave out all the fluff and deliver just enough detail to equip us to move to the next part of his presentation: Evolutionary Database Development.
This second part of the book covers *a lot* of ground. After a well-crafted appeal for flexibility as a major success factor in software development, Ambler introduces the principles and practices of his own "Agile Model-Driven Development" approach, then a concise discussion of Test-Driven Development, also known as "test-first programming". This is a very brief chapter, and I wish Ambler had developed these concepts a bit more, but he has much bigger fish to fry in this book. His discussion of the need for, and practices of, database refactoring will be provocative for many data people. In my own consulting experience the "rot" or "smell" of database entropy is everywhere. The rigor of the original data models is lost under the pressure of schedule, or the inertia of inexperienced persons not taking the time to think about the downstream effects of reusing a table column for an obscure and transient purpose...which soon becomes permanent. The most significant chapter in the second part discusses mapping objects to relational databases. Ambler has written often and extensively about the object-relational "impedance mismatch", and this chapter offers the programmer and DBA much to think about.
A theme that runs throughout the entire book is what Ambler calls the "role of the agile DBA". These brief discussions, almost sidebars in their presentation, are aimed squarely at DBAs working on agile, OO projects. Most OO developers will kill for a DBA who actually supports the software effort rather than being an institutionalized impediment. Ambler's tips to the "agile DBA" are worth the price of the book, IMHO.
Part 3 is a collage of database concepts that are essential for software developers to understand if they are to be successful as a programming and data team. The topics include referential integrity, access control, concurrency issues and control, transactions and their ACID properties, with a brief discussion of both database transactions and object transactions -- and they are not the same. Very important stuff, and it is my experience that many application programmers have only the barest understanding of these critical technical issues--especially data-specific issues such as two-phase commits. It's all here.
The last part of the book reflects the beginning: how can you become agile, and how can you bring agility into your organization? Ahh, this is going to be hard for some people, and some companies. But it can be done, if approached patiently, with sensitivity for your existing corporate culture. And the reality of the cultural mismatch is something Ambler addresses throughout this book. This is why he calls the agile DBA a "peacemaker". This is why he calls upon us to be "generalizing specialists", so we can see that there is more to software than objects, and certainly more than data alone.
Were these reviews helpful? Let us know