In the article you stated "you'll have to store your code in a file and execute it as an OS task using wscript.exe" but what you really want to use is cscript.exe. This way, all your WScript.Echo calls get sent to the standard output and if you're saving the job step output to a log file, this will get sent to your log file. Unfortunately, if you're using wscript.exe, the Echo tries to pop up a message box which everyone knows is a bad idea on a production system!

Thanks for this series on jobs, it has given me a lot to think about as I have six servers to manage and each one has 30+ databases and lots of jobs to go with them!

Bryant E. Byrd, MCDBA

SQL Server DBA/Systems Engineer

Intellithought, Inc.

bbyrd@intellithought.com