osql comes with the client tools. If you have Enterprise Manager, then
you've got it.
H:\>osql /?
usage: osql [-U login id] [-P password]
[-S server] [-H hostname] [-E trusted connection]
[-d use database name] [-l login timeout] [-t query timeout]
[-h headers] [-s colseparator] [-w columnwidth]
[-a packetsize] [-e echo input] [-I Enable Quoted
Identifiers]
[-L list servers] [-c cmdend] [-D ODBC DSN name]
[-q "cmdline query"] [-Q "cmdline query" and exit]
[-n remove numbering] [-m errorlevel]
[-r msgs to stderr] [-V severitylevel]
[-i inputfile] [-o outputfile]
[-p print statistics] [-b On error batch abort]
[-O use Old ISQL behavior disables the following]
<EOF> batch processing
Auto console width scaling
Wide messages
default errorlevel is -1 vs 1
[-? show syntax summary]
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 17, 2002 7:14 AM
To: [EMAIL PROTECTED]
Subject: RE: [OT] SQL console for MSSQL
Importance: Low
> VNC or
> Odbc over Access.
> kris
hm, sounds like much overhead... I thought there's some easy Dosbox tool
like for DB2 for a few quick statements... cause even with vnc I'd have
to click me through that Enterprise Manager until i see some contents of
a table...
Lars
