This is the final part of Alex's ground-breaking series on unit-testing Transact-SQL code. Here, he shows how you can test the way that your application handles database-related errors such as constraint-violations or deadlocks. With a properly-constructed test-harness you can ensure that the end-user need never see the apparent gobbledegook of database system error messages, and that they are properly and robustly handled by the application.  Read more...

Often developers are tasked with not only developing functional code, but also with ensuring that the code they develop scales well and performs in the application environment.  Read more...

The need to test a program that accesses and manipulates a back-end SQL Server® database is very common. In many such cases, the application interacts with the back-end data through the use of SQL stored procedures. In this type of scenario, you can think of the stored procedures as auxiliary methods of the system under test; and they must therefore be tested just like any other module in the system.  Read more...

This article from MSDN discusses the benefits of TDD and bringing unit testing to your database development.  Read more...

This article looks at fuzzy testing and how to build a provider for your own use.  Read more...