Developers can get so used to relying on computers for everything that they can forget how useful it can be in the design process to elicit and refine ideas whilst working in groups, using a sketchbook, pencils and crayons. Sometimes we all need a jolt to force us to take a different approach to solving software design problems.
When a team is developing a database application, it is a mistake to believe that deployment is a simple task. It isn’t. It has to be planned, and scripted. Alexander Karmanov describes many of the problems you’re likely to meet, and provides an example solution that aims to save the DBA from the nightmare complexity of an unplanned deployment.
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.
SQL Server source code analysis and management add database security by debugging and testing SQL applications. Learn about SQL source code analysis.
Greg Larsen looks at one way to design your database connection strategy to simplify changing application connections so you can plug-n-play databases with less administrative overhead when the need arises.