System Development Life Cycle

SQLServerCentral Article

Putting Unit Tests to Work

  • Article

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.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(1)

You rated this post out of 5. Change rating

2008-01-16 (first published: )

7,915 reads

SQLServerCentral Article

Writing Maintainable Code

  • Article

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.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2006-08-07

9,716 reads

SQLServerCentral Article

Unit Testing and Code Generation

  • Article

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.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(4)

You rated this post out of 5. Change rating

2006-06-20

17,834 reads

External Article

SQL Server Performance Testing

  • Article

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

Blogs

T-SQL Tuesday #204 – Are blogs still relevant? (Roundup)

By

I did not expect 27 responses to my T-SQL Tuesday #204 invitation, but it...

Build vs Buy AI: When to adopt, partner, build or buy

By

Should you adopt an off-the-shelf AI tool, partner with a specialist, build in-house, or...

What's New in SQL Server for the Developer: SQL Server 2012

By

Part 1 of my What's New in SQL Server for the Developer series. IIF,...

Read the latest Blogs

Forums

Switching Schema II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Switching Schema II

A Practical Approach to Automating SQL Server Email Notifications

By Kunal Rathi

Comments posted to this topic are about the item A Practical Approach to Automating...

Data Lost in the Cloud

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Data Lost in the Cloud

Visit the forum

Question of the Day

Switching Schema II

I run this query:

SELECT 
 s.name AS schemaname
 , o.name AS objectname
 FROM sys.objects o
 INNER JOIN sys.schemas s ON s.schema_id = o.schema_id
 WHERE o.name = 'Beer'
I get two rows back for the objects, named dbo.beer and etl.beer. Both the tables have identical schemas and are not partitioned. There are 25 rows in dbo.beer and 0 rows in etl.beer. I run this code:
ALTER TABLE dbo.beer switch TO etl.beer
What happens?

See possible answers