Testing is an important part of any software development process, but it's a part that many of us skimp on or ignore because of the tedious nature of testing. Longtime author Grant Fritchey has been working with Visual Studio Team Edition for Database Professionals and has written us an article on how you can make your unit testing easier.
2008-01-16 (first published: 2007-02-01)
7,856 reads
Learn how to keep track of previous versions of code in case your next upgrade doesn't go well from SQL Server guru Tim Chapman.
2007-01-15
2,928 reads
The same ANSI Standard SQL query can run against identical data on SQL Server and Oracle and return different results. So just because your application issues ANSI standard SQL, don't assume it's portable.
2006-11-09
2,041 reads
No developer or DBA wants to be told how to write their code. Everyone has their own style, but this can cause problems in a team environment where different people need to work on the same section of code. New author Pam Abdulla brings us a few simple techniques that can help you write more maintainable code.
2006-08-07
9,667 reads
This article adds some handy reporting capabilities to the new load testing tool in Visual Studio 2005 Team System.
2006-07-04
1,459 reads
Although the challenges of designing and developing an embedded software package are obvious, the effort of providing remote support for the deployed application is often underestimated.
2006-06-22
2,581 reads
One of the fundamental skills a developer needs is the ability to test their code. Most people don't really do a good job, partly because they don't have a good process and leave testing until the end. Grant Fritchey brings us a new method of unit testing T-SQL stored procedures that can help you build automated tests for your code.
2006-06-20
17,775 reads
This (new) design bothered me. It violated one of the fundamentals that I'd learned and read about for years; namely keeping the primary key small and narrow. It also looked like it would be difficult to maintain. Finally, after arguing back and forth about the merits and drawbacks of each of the designs, we decided that testing them was the only way to be sure
2006-06-02
4,359 reads
If you deliver applications to a customer, then you have struggled with the challenges of updating schemas as they change. New author Serhiy Snisarenko brings us his comprehensive process and code to make this task easier.
2006-04-19
10,331 reads
Most software projects fail. Only about a quarter are completely successful. About half are late and over budget and the remaining quarter just fade into oblivion. What if there was a simple way to ensure your project’s success? There is, and it’s all about starting out in the right way
2006-03-07
3,274 reads
By James Serra
I’m honored to be hosting T-SQL Tuesday — edition #192. For those who may...
By Vinay Thakur
Continuing from Day 2 , we learned introduction on Generative AI and Agentic AI,...
Quite the title, so let me set the stage first. You have an Azure...
Comments posted to this topic are about the item A Quick Restore
Comments posted to this topic are about the item Guarding Against SQL Injection at...
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers