Testing Times for the Team
Unit testing has been much slower to catch on in the database world than amongst application code developers, but the times they are a-changing and there has been much talk in recent years about unit-testing database code and even questions about agile development practices amongst database professionals. How does this work in practice though? What happens when we have a team developing using a variety of technologies - T-SQL, .Net, SSIS for example? How can we handle situations where we need to work with different versions, named and default instances of SQL Server, different drive configurations? Can it all be made to work? This session looks at some of these challenges and proposes some possible ways to address them. No doubt you've got your own experiences to share as well.
Sorry, there are no downloads available for this session.
Andrew Whettam is a Consultant for Information Management Group and has previously led the Database and Business Intelligence teams for 3M and Capital One respectively. He works with both transactional and analytical databases and has modelled, designed and developed database systems across a variety of industry sectors. Recent IMGROUP projects have included roles as Data Modeller for a major financial institution and Data Architect for a large conglomerate. Past experience includes a number of high profile government projects. He has worked with all versions of SQL Server since SQL 7.0.
The video is not available to view online.