Search
Home
Articles
Backup
Books
Certification
FAQ
Products
Replication
Scripts
Seminars
Training
TSQL

MSDN Fourms
Fort Worth SSUG
Oklahoma City SSDG

Resume

Champion Valley Pens

SQL-Programmer IX SP2 with TSQL Debugger 1 2 3 4 5 6 7 8 9 10 11 12

The SPDW, SQL-Programmer Development Window, is where you will spend most of your time.  One of the things I like about SQL-Programmer's color-coded syntax is that it is an intelligent color coding.  It can code an integer differently from a datetime or a string value.  What it does well is that it codes the variables the color corresponding to their datatype which helps track them easily.  The window below may look rather simple, but it packs a lot of functionality.  The Prologue and Epilogue give you advanced capabilities that you won't find anywhere else.  The Prologue allows you to specify a script to execute before running the stored procedure.   The Epilogue is where you would specify a script to run after the procedure completes.  Combining these two allows you to set up some rather complex testing scenarios where you can create tables, fill them with data, execute other procedures, etc. before and after executing the procedure you are working on.  The arguments tab contains a grid where you can input arguments to use.  The Privileges tab displays the object privileges.  The Dependencies tab displays any dependencies.  The Activity Log tracks each operation that was performed such as opening, execution, saving, modifications, etc.  The results tab will contain the results of the stored procedure and any other actions taken in the Prologue and Epilogue.  Now you may say that is a lot of work that will be lost as soon as you close this window.  The nice thing about this is the ability to save an SPDW to a file.  This means that you can setup a variety of testing scenarios with different arguments, Prologues, Epilogues, save them to files, and rerun them at a later time without losing any work.  This gives you one of the most powerful, self contained testing methods I have seen.  This single feature by itself can dramatically streamline testing procedures since you don't have to keep recreating them.

sql-programmerix-13.gif (23861 bytes)

SQL-Programmer IX SP2 with TSQL Debugger 1 2 3 4 5 6 7 8 9 10 11 12

Michael R. Hotek

All content on this site, except where noted, represents an original work of Michael R. Hotek and is protected by applicable copyright laws. The SQL Server FAQ is the sole work of Neil Pike. No page, portion of a page, or download may be used for commercial purposes in whole or in part without the express, written permission of the applicable author.