The problem is a need to closely monitor multiple servers jobs running custom applications and performance. This is accomplished easily by TSQL scripts, then when an issue is found able by changing certain parameters drill down to narrow or broad overview of application progression. When intervention is required SQL Server Management Studio is used to resolve issues. I oversee several applications adding users/codes periodically all day. We are rewriting the app but for now must do research and verification then manually enter user/codes. This is done very nicely by existing parameterized scripts. SQLCMD is nice to run a script but does not seem to lend itself to an all day monitoring of application DB's by script like ISQLW does. SQL Management Studio will allow me to maintain these windows/scripts but it takes so long to find the correct window when have a large number of windows open and running. Really nice to split off scripts that I just want to monitor periodically, with no chance of accidentally close/save/run if mixed in with development work windows. Frenzied multitasking does have a tendency biting you when you least can afford it.