Be the first to get a complete picture of the health and performance of your business critical DB2 database environment using the new NiCE DB2 smart Plug-In 4.30. The NiCE DB2 smart Plug-In delivers first-rate monitoring for business critical, highly dynamical database environments. Leverage your existing investment and reduce costs, save time and build efficiencies now.

If you missed the first 2 tips, go back and read 5 Tips to Avoid Deadlocks in Amazon RDS (Part 1), and then come back for the last 3 tips on deadlock avoidance. Once again, I want to re-emphasize that RDS is not actually capable of creating deadlocks — it merely reports them from the underlying database engine.

Last week, I wrote A Beginner’s Guide to Deadlocks in Amazon RDS. This week, I’d like to lay out my 10 years of experience about how to avoid deadlocks altogether. Often times, this will be out of the hands of operations people, but you can still move for dev changes based on issues in production. The more knowledgeable you are about deadlocks in general, the more they will lean on you as a resource with wisdom, not a totalitarian barking rules.

Although AWS sometimes feels like magic, it’s just software that controls capacity and allocation on their previously provisioned hardware. RDS is one of the services that can feel especially magic, because of the general difficulty and drudgery required to set up and manage a production database. In a matter of minutes, anyone can have a production database, complete with replication, automatic failover, backup schedules, and point-in-time recovery.

Hearing you’re getting MySQL is like hearing you’ve been “volunteered” to pet sit your neighbor’s rabid ferret: There’s confusion, mild panic and the frustrating realization that someone else is saving money because you’re doing all the hard work. Open source: fantastic for IT budgets, not so fantastical for DBAs.