Search
InstantDoc ID
GO

Browse By: Author | Issue

June 22, 2005 09:22 PM

Pep Up T-SQL Procedure Testing

Use dynamic queries and Web reports to automate your tests
Rating: (0)
Dan Sawyer
SQL Server Magazine
InstantDoc ID #46433
Used to be, procedure testing was a last-minute sanity check before releasing a new procedure: "Does the procedure execute cleanly and complete its assigned work?" If you answered yes, you could release the procedure and move on. Few busy DBAs had time to worry about atypical usage scenarios such as illegal parameter values, missing data, or unavailable objects such as work tables. But this straightforward approach no longer works. We now know that stored procedures are just like other software:...

...This article is for paid Professional Members only.

Already a Professional Member? Please log in now:

NOT A PROFESSIONAL MEMBER? YOU CHOOSE:

Professional Membership

Monthly

Annual

VIP Membership

Monthly

Annual

Compare Member Benefits

Add a Comment

Marcos, thanks for your comments. I'll look into asking one of our authors to do a follow-up article that provides a testing solution that works in the way you suggest. Thanks for reading!
Anne Grubb, Web site strategic editor, SQL Server Magazine

Anne12/13/2007 1:04:33 PM

This is now new at all. In fact, the problem that matters the most is how good is your test case, and the work needed "prepare" for the test. As the author said if you have to check data in tables that change with INSERT, UPDATE or DELETE operations, you still have to do it manually, since automating this is not easy. I would like to see a test tool that check the dependencies by it self and create a test load that includes the data needed in the database for the tests. It will be really useful.

Marcos12/6/2007 1:18:16 PM

You must log on before posting a comment.

Are you a new visitor? Register Here

© 2010 Penton Media, Inc.

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.