June 17, 2009 at 6:20 am
I use Microsoft SQL Server Management Studio for development/debug production/user support/system maintenance/... but need to contentiously monitor specific systems and continuously run 1 or 2 TSQL update scripts all day long. I have found it easiest to do all generic task in Management Studio (8-15 windows) and separate (usually 2 occasionally max 4 windows) application monitoring/update scripts in ISQLW for fast and easy locating, modify, and running. I have checked advertisers but have not found anything as simple as ISQLW and with small system footprint. VB Apps really is over kill and is not as flexible. Any one know of or use an alternative to ISQLW for very small footprint and flexibility to run/tweak/display TSQL scripts? I already split the display window to Management Studio for development and scripts get lost within all open windows.
June 17, 2009 at 7:35 am
Have you looked at SQLCMD? It's the replacement for osql which itself was the replacement for isql.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 17, 2009 at 7:38 am
Yeah, I was going to suggest SQLCMD as well.
Plus, why are you manually opening all kinds of windows in SSMS to do manual updates all day long? You should be able to script out processes and schedule them with SQL Agent or set up triggers and not have to sit there manually running tons of different scripts to keep the system up.
Also, you might look into PowerShell. It provides more programming ability without all the overhead of VB or C#.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 17, 2009 at 3:55 pm
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.
June 18, 2009 at 5:31 am
I don't understand what ISQLW does that SQLCMD does not?
From the sounds of it, you really might benefit from Powershell.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 18, 2009 at 5:45 am
Oh, sorry. I misread. ISQLW is Query Analyser. It's ISQL that SQLCMD's a replacement for.
I'm curious why management studio's not acceptable. You can always open multiple copies of it if you like.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 18, 2009 at 6:17 am
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.
June 18, 2009 at 6:23 am
Have you looked at Toad? It's 3rd party and not free, but I've heard good things about it. Other option if you still have 2000 disk lying around is to install QA. It connects to SQL 2005, haven't tried 2008. Might be worth a try.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 18, 2009 at 6:34 am
I just tried QA against 2008. It works. Nominally. I haven't run a full-on regression test or anything.
I'm sorry too. I thought you, the OP, were trying to find ways to automate what sounds like an awful lot of thrash.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 18, 2009 at 10:15 am
I greatly appreciate your help on my conundrum. I used Toad with Oracle (Nice) but it looks like it has a large footprint also. I had a copy of needed DLLs from 2000, but someone deleted them when cleaning up servers, and was hoping to use a currant app so will not have to continually face this issue when changing workstations or upgrades. I have seen a Web Browser App at previous employment that you could enter a script and it would display the result set, but have not figured it out yet. Thanks a million.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply