Maybe I have misunderstood the roll of SQLCMD? What I have read is that it is a fabulous tool to run a SQL script from a command line, but what I need is to leave the connection open to repeatedly run the script for monitoring, and then tweak the parameters/code to explore the range of anomalies possible in custom DB applications. Power shell appears to be a great ?reporting? tool to display known predetermined scripts, not browsing or do (Research/Validate/Update) table contents. Management Studio can open multiple copies (NIiiicccceee) but it is resource intensive just to display a result grid. So when you open two-three DTS/Visual Studio for migrating packages (2000-2005-2008), Outlook, Word, Excel, Access, Windows Explorer, couple Internet Explorers, Job Activity Monitor, Remote Desktop Connections,... all on one laptop masquerading as a work station.