I am having an awfull time trying to get my code to run in ISQLW
This is the code
call isqlw -S scrbbususcnc01 -d master -U jdionne -P ttttttt -Q "Exec xp_sendmail 'eddens, david; dionne, jim', '(scrbbususcnc01) Success - JOC Loaded LineMkt Support Tables', @.subject = '(scrbbususcnc01) Success - JOC Loaded LineMkt Support Tables'" -o \\scrbbususcnc01\Maersk_DW\RKMS\logs\TestIncrement al.log -s "|"
Every time i run this I get a window listing all of the switches for isql and the -Q is not listed. Can someone please send me some insight on this.
JimSounds like you want OSQL, instead of ISQL. ISQLW is Query Analyzer. Bit too graphical a tool, I think to be commandline friendly. You may want to edit out your password, too.|||Originally posted by MCrowley
Sounds like you want OSQL, instead of ISQL. ISQLW is Query Analyzer. Bit too graphical a tool, I think to be commandline friendly. You may want to edit out your password, too.
using isql did the job
Thanx
Showing posts with label isqlw. Show all posts
Showing posts with label isqlw. Show all posts
Monday, February 20, 2012
isqlw.exe
Hello,
I notice that the name of the Query Analyzer program (formerly
known as ISQL/W) is still isqlw.exe in SQL Server 2000. I am
curious as to where the name ISQL/W came from.
Feedback welcome,
Best Regards,
Neil<nzanella@.cs.mun.ca> wrote:
> Hello,
> I notice that the name of the Query Analyzer program (formerly
> known as ISQL/W) is still isqlw.exe in SQL Server 2000. I am
> curious as to where the name ISQL/W came from.
> Feedback welcome,
> Best Regards,
> Neil
Neil,
It's always been my understanding that the "w" in isqlw stood for Windows:
isql was the original command line interface to SQL Server and isqlw was the
GUI "version" of the same concept.
Craig|||(nzanella@.cs.mun.ca) writes:
> I notice that the name of the Query Analyzer program (formerly
> known as ISQL/W) is still isqlw.exe in SQL Server 2000. I am
> curious as to where the name ISQL/W came from.
In the begiinning there was Sybase, and their interactive interface to
SQL Server was ISQL - Interacticve SQL.
Microsoft teamed up with Sybase and supplied the Windows version of
SQL Server.
Later Microsoft cancelled the partnership with Sybase and the two
went on to develop SQL Server each on their own. Microsoft augmented
the toolset with a graphical interface and this was named ISQL/W,
where W certainly was for Windows. ISQL/W hung around until 6.5.
For SQL 7, Microsoft developed a new tool, the Query Analyzer with
richer set of functionality and which used ODBC to connect and not
DB-Library. For reasons unknown to me, the executable retained the
name isqlw.exe.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
isqlw won't start
Hi there,
Meanwhile I have solved the problem. I have installed SP3 and have
repaired the registry entries. After that Query Analyzer worked fine.
Tried rebooting? More importantly, have you installed any service pack
for SQL 2000? You should install at least SP3, but there is an SP4 as
well. There is a serious security threat in SQL 2000 RTM which is fixed
in SP3. (The Slammer worm.)
I tried to install MS SQL Server 2000 on my desktop computer after
uninstalling a version 7 instance. Everything worked fine. Using
Enterprise Manager I can manage databases and the database enginge itself.
My problem is now, that ISQLW.exe, i.e Query Analayzer won't start. The
taskmanager shows a process isqlw.exe but nothing happens. MSSQL Log
files give no hints, neither does the Windows 2000 event log.
I assume a problem with the previously installed MSSQL7 version, but
walked through the registry as well.
Are there any hints why isqlw doesn't want to speak to me?
Thanks,
AndreAndre Ma@.ss schrieb:
Quote:
Originally Posted by
Are there any hints why isqlw doesn't want to speak to me?
Meanwhile I have solved the problem. I have installed SP3 and have
repaired the registry entries. After that Query Analyzer worked fine.
Thanks,
Andre|||Andre Ma@.ss (Samweis11@.gmx.de) writes:
Quote:
Originally Posted by
I tried to install MS SQL Server 2000 on my desktop computer after
uninstalling a version 7 instance. Everything worked fine. Using
Enterprise Manager I can manage databases and the database enginge itself.
>
My problem is now, that ISQLW.exe, i.e Query Analayzer won't start. The
taskmanager shows a process isqlw.exe but nothing happens. MSSQL Log
files give no hints, neither does the Windows 2000 event log.
>
I assume a problem with the previously installed MSSQL7 version, but
walked through the registry as well.
>
Are there any hints why isqlw doesn't want to speak to me?
Tried rebooting? More importantly, have you installed any service pack
for SQL 2000? You should install at least SP3, but there is an SP4 as
well. There is a serious security threat in SQL 2000 RTM which is fixed
in SP3. (The Slammer worm.)
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
ISQLW in 2005?
I'm sure that I'm not the first to complain about this, but it bothers
me that it seems that MS is now forcing us to use this new bloated SQL
management studio. Don't get me wrong, it does a lot and is a great
management tool. However, nearly everything I do with SQL Server I do
through script. In fact, in the past, I avoided using EM at all costs
for performance reasons. Not everyone has the luxury of top-of-the-line
hardware, SANs, fast networks and local servers. Is there a lightweight
tool for 2005 like the old-school Query Analyzer?
-AlanHi Alan,
Your sentiment is shared by a lot of people, once you get used to the tool
though its fantastic - I write mainly in DDL myself rather than use the GUI.
You can use iSQL from SQL 2000 against a 2005 database so for existing
installations you'd be ok, but, give the management studio a try and you'll
find once you get used to the slightly different way of working then you'll
gain productivity.
Tony.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"Alan Samet" <alansamet@.gmail.com> wrote in message
news:1136299129.784559.94230@.g43g2000cwa.googlegroups.com...
> I'm sure that I'm not the first to complain about this, but it bothers
> me that it seems that MS is now forcing us to use this new bloated SQL
> management studio. Don't get me wrong, it does a lot and is a great
> management tool. However, nearly everything I do with SQL Server I do
> through script. In fact, in the past, I avoided using EM at all costs
> for performance reasons. Not everyone has the luxury of top-of-the-line
> hardware, SANs, fast networks and local servers. Is there a lightweight
> tool for 2005 like the old-school Query Analyzer?
> -Alan
>|||If you do everything through scripts and want to minimize overhead, you
might want to just use sqlcmd.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Alan Samet" <alansamet@.gmail.com> wrote in message
news:1136299129.784559.94230@.g43g2000cwa.googlegroups.com...
> I'm sure that I'm not the first to complain about this, but it bothers
> me that it seems that MS is now forcing us to use this new bloated SQL
> management studio. Don't get me wrong, it does a lot and is a great
> management tool. However, nearly everything I do with SQL Server I do
> through script. In fact, in the past, I avoided using EM at all costs
> for performance reasons. Not everyone has the luxury of top-of-the-line
> hardware, SANs, fast networks and local servers. Is there a lightweight
> tool for 2005 like the old-school Query Analyzer?
> -Alan
>|||Nobody will prevent you from using the successor for OSQL --> SQLCMD
;-)
HTH, Jens Suessmeyer.|||At least that will work until the DOS prompt is retired from Windows. :-0
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1136300386.513873.242110@.z14g2000cwz.googlegroups.com...
> Nobody will prevent you from using the successor for OSQL --> SQLCMD
> ;-)
> HTH, Jens Suessmeyer.
>
me that it seems that MS is now forcing us to use this new bloated SQL
management studio. Don't get me wrong, it does a lot and is a great
management tool. However, nearly everything I do with SQL Server I do
through script. In fact, in the past, I avoided using EM at all costs
for performance reasons. Not everyone has the luxury of top-of-the-line
hardware, SANs, fast networks and local servers. Is there a lightweight
tool for 2005 like the old-school Query Analyzer?
-AlanHi Alan,
Your sentiment is shared by a lot of people, once you get used to the tool
though its fantastic - I write mainly in DDL myself rather than use the GUI.
You can use iSQL from SQL 2000 against a 2005 database so for existing
installations you'd be ok, but, give the management studio a try and you'll
find once you get used to the slightly different way of working then you'll
gain productivity.
Tony.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"Alan Samet" <alansamet@.gmail.com> wrote in message
news:1136299129.784559.94230@.g43g2000cwa.googlegroups.com...
> I'm sure that I'm not the first to complain about this, but it bothers
> me that it seems that MS is now forcing us to use this new bloated SQL
> management studio. Don't get me wrong, it does a lot and is a great
> management tool. However, nearly everything I do with SQL Server I do
> through script. In fact, in the past, I avoided using EM at all costs
> for performance reasons. Not everyone has the luxury of top-of-the-line
> hardware, SANs, fast networks and local servers. Is there a lightweight
> tool for 2005 like the old-school Query Analyzer?
> -Alan
>|||If you do everything through scripts and want to minimize overhead, you
might want to just use sqlcmd.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Alan Samet" <alansamet@.gmail.com> wrote in message
news:1136299129.784559.94230@.g43g2000cwa.googlegroups.com...
> I'm sure that I'm not the first to complain about this, but it bothers
> me that it seems that MS is now forcing us to use this new bloated SQL
> management studio. Don't get me wrong, it does a lot and is a great
> management tool. However, nearly everything I do with SQL Server I do
> through script. In fact, in the past, I avoided using EM at all costs
> for performance reasons. Not everyone has the luxury of top-of-the-line
> hardware, SANs, fast networks and local servers. Is there a lightweight
> tool for 2005 like the old-school Query Analyzer?
> -Alan
>|||Nobody will prevent you from using the successor for OSQL --> SQLCMD
;-)
HTH, Jens Suessmeyer.|||At least that will work until the DOS prompt is retired from Windows. :-0
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1136300386.513873.242110@.z14g2000cwz.googlegroups.com...
> Nobody will prevent you from using the successor for OSQL --> SQLCMD
> ;-)
> HTH, Jens Suessmeyer.
>
Isqlw for sql server mobile edition (sql ce 3)
In sql ce 2.0 in window ce 2003, I use isqlw20.exe to create database and table. Developed application with eVC++ 4.0
Now I have to use window mobile 5, VS 2005 for native C++ development, sql server mobile edition, but I can't found isqlw for this version of sql. I do not have sql server install in my desktop PC. So how could I create database and table with the pocket pc's database ?
Thanks.
ISQLW30.EXE is available from SQL Mobile 3.0 for Pocket PC and Pocket PC Phone Edition Devices/Emulators.
If you have installed SQL Mobile 3.0 cabs, you should find a shortcut getting created automatically in Start Menu.
Thanks,
Laxmi Narsimha Rao ORUGANTI, SQL Mobile, Microsoft Corporation
isqlw connection problems
I'm trying to connect to remote sql servers. I can connect to and work with
the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it times
out trying to connect with the error messages:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not
exist or
access denied.
Followed by:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Conn
ect())
Why can't I connect with Query Analyzer, but I can with Enterprise Manager?
How do I resolve this?
I have no problems using Query Analyzer and connecting to my local sql
servers.
I have no problems using Query Analyzer to connect to local and remote sql
servers on my other computer, just with this one computer.
Thanks,
Wayne SheffieldFYI: I did check out http://support.microsoft.com/?kbid=328306, but nothing
there helped out.
Thanks,
Wayne
"Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> I'm trying to connect to remote sql servers. I can connect to and work
with
> the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it
times
> out trying to connect with the error messages:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does n
ot exist or
> access denied.
> Followed by:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Co
nnect())
> Why can't I connect with Query Analyzer, but I can with Enterprise
Manager?
> How do I resolve this?
> I have no problems using Query Analyzer and connecting to my local sql
> servers.
> I have no problems using Query Analyzer to connect to local and remote sql
> servers on my other computer, just with this one computer.
> Thanks,
> Wayne Sheffield
>|||Are you using the same account as EM uses?
Andrew J. Kelly SQL MVP
"Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> I'm trying to connect to remote sql servers. I can connect to and work
with
> the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it
times
> out trying to connect with the error messages:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does n
ot exist or
> access denied.
> Followed by:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Co
nnect())
> Why can't I connect with Query Analyzer, but I can with Enterprise
Manager?
> How do I resolve this?
> I have no problems using Query Analyzer and connecting to my local sql
> servers.
> I have no problems using Query Analyzer to connect to local and remote sql
> servers on my other computer, just with this one computer.
> Thanks,
> Wayne Sheffield
>|||Yes. When you open QA this way, it uses the EM account settings.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uiF7z8daEHA.2840@.TK2MSFTNGP11.phx.gbl...
> Are you using the same account as EM uses?
> --
> Andrew J. Kelly SQL MVP
>
> "Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
> news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> with
> times
or[vbcol=seagreen]
> Manager?
sql[vbcol=seagreen]
>
the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it times
out trying to connect with the error messages:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not
exist or
access denied.
Followed by:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Conn
ect())
Why can't I connect with Query Analyzer, but I can with Enterprise Manager?
How do I resolve this?
I have no problems using Query Analyzer and connecting to my local sql
servers.
I have no problems using Query Analyzer to connect to local and remote sql
servers on my other computer, just with this one computer.
Thanks,
Wayne SheffieldFYI: I did check out http://support.microsoft.com/?kbid=328306, but nothing
there helped out.
Thanks,
Wayne
"Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> I'm trying to connect to remote sql servers. I can connect to and work
with
> the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it
times
> out trying to connect with the error messages:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does n
ot exist or
> access denied.
> Followed by:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Co
nnect())
> Why can't I connect with Query Analyzer, but I can with Enterprise
Manager?
> How do I resolve this?
> I have no problems using Query Analyzer and connecting to my local sql
> servers.
> I have no problems using Query Analyzer to connect to local and remote sql
> servers on my other computer, just with this one computer.
> Thanks,
> Wayne Sheffield
>|||Are you using the same account as EM uses?
Andrew J. Kelly SQL MVP
"Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> I'm trying to connect to remote sql servers. I can connect to and work
with
> the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it
times
> out trying to connect with the error messages:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does n
ot exist or
> access denied.
> Followed by:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Co
nnect())
> Why can't I connect with Query Analyzer, but I can with Enterprise
Manager?
> How do I resolve this?
> I have no problems using Query Analyzer and connecting to my local sql
> servers.
> I have no problems using Query Analyzer to connect to local and remote sql
> servers on my other computer, just with this one computer.
> Thanks,
> Wayne Sheffield
>|||Yes. When you open QA this way, it uses the EM account settings.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uiF7z8daEHA.2840@.TK2MSFTNGP11.phx.gbl...
> Are you using the same account as EM uses?
> --
> Andrew J. Kelly SQL MVP
>
> "Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
> news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> with
> times
or[vbcol=seagreen]
> Manager?
sql[vbcol=seagreen]
>
isqlw connection problems
I'm trying to connect to remote sql servers. I can connect to and work with
the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it times
out trying to connect with the error messages:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
Followed by:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect())
Why can't I connect with Query Analyzer, but I can with Enterprise Manager?
How do I resolve this?
I have no problems using Query Analyzer and connecting to my local sql
servers.
I have no problems using Query Analyzer to connect to local and remote sql
servers on my other computer, just with this one computer.
Thanks,
Wayne Sheffield
FYI: I did check out http://support.microsoft.com/?kbid=328306, but nothing
there helped out.
Thanks,
Wayne
"Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> I'm trying to connect to remote sql servers. I can connect to and work
with
> the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it
times
> out trying to connect with the error messages:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Followed by:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect())
> Why can't I connect with Query Analyzer, but I can with Enterprise
Manager?
> How do I resolve this?
> I have no problems using Query Analyzer and connecting to my local sql
> servers.
> I have no problems using Query Analyzer to connect to local and remote sql
> servers on my other computer, just with this one computer.
> Thanks,
> Wayne Sheffield
>
|||Are you using the same account as EM uses?
Andrew J. Kelly SQL MVP
"Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> I'm trying to connect to remote sql servers. I can connect to and work
with
> the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it
times
> out trying to connect with the error messages:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Followed by:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect())
> Why can't I connect with Query Analyzer, but I can with Enterprise
Manager?
> How do I resolve this?
> I have no problems using Query Analyzer and connecting to my local sql
> servers.
> I have no problems using Query Analyzer to connect to local and remote sql
> servers on my other computer, just with this one computer.
> Thanks,
> Wayne Sheffield
>
|||Yes. When you open QA this way, it uses the EM account settings.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uiF7z8daEHA.2840@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Are you using the same account as EM uses?
> --
> Andrew J. Kelly SQL MVP
>
> "Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
> news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> with
> times
or[vbcol=seagreen]
> Manager?
sql
>
the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it times
out trying to connect with the error messages:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
Followed by:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect())
Why can't I connect with Query Analyzer, but I can with Enterprise Manager?
How do I resolve this?
I have no problems using Query Analyzer and connecting to my local sql
servers.
I have no problems using Query Analyzer to connect to local and remote sql
servers on my other computer, just with this one computer.
Thanks,
Wayne Sheffield
FYI: I did check out http://support.microsoft.com/?kbid=328306, but nothing
there helped out.
Thanks,
Wayne
"Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> I'm trying to connect to remote sql servers. I can connect to and work
with
> the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it
times
> out trying to connect with the error messages:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Followed by:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect())
> Why can't I connect with Query Analyzer, but I can with Enterprise
Manager?
> How do I resolve this?
> I have no problems using Query Analyzer and connecting to my local sql
> servers.
> I have no problems using Query Analyzer to connect to local and remote sql
> servers on my other computer, just with this one computer.
> Thanks,
> Wayne Sheffield
>
|||Are you using the same account as EM uses?
Andrew J. Kelly SQL MVP
"Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> I'm trying to connect to remote sql servers. I can connect to and work
with
> the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it
times
> out trying to connect with the error messages:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Followed by:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect())
> Why can't I connect with Query Analyzer, but I can with Enterprise
Manager?
> How do I resolve this?
> I have no problems using Query Analyzer and connecting to my local sql
> servers.
> I have no problems using Query Analyzer to connect to local and remote sql
> servers on my other computer, just with this one computer.
> Thanks,
> Wayne Sheffield
>
|||Yes. When you open QA this way, it uses the EM account settings.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uiF7z8daEHA.2840@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Are you using the same account as EM uses?
> --
> Andrew J. Kelly SQL MVP
>
> "Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
> news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> with
> times
or[vbcol=seagreen]
> Manager?
sql
>
isqlw and std out
When using the ISQLW command line I woul like to output to screen rather
than file. How can I do this ?
Hi GMG,
Thanks for your post.
From you descriptions, I understood your ISQLW command line will
automatically output to a file instead of screen.
However, ISQLW will launch Query Analyzer and osql is the command line for
SQL Server. Both QA and osql will defaultly output to screen instead of
files. Would you please show me more detailed steps about your scenario?
More detailed informaiton, I believe, will make us closer to the resolution.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||I am automating a number of scripts to be run via ISQL, but I have found
particular ANSI characters are corrupted. When running ISQLW via the command
line everything is fine, but it outputs to file which is not ideal I would
the output summary to display to the DOS screen.
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:WjTmruQrFHA.3532@.TK2MSFTNGXA01.phx.gbl...
> Hi GMG,
> Thanks for your post.
> From you descriptions, I understood your ISQLW command line will
> automatically output to a file instead of screen.
> However, ISQLW will launch Query Analyzer and osql is the command line for
> SQL Server. Both QA and osql will defaultly output to screen instead of
> files. Would you please show me more detailed steps about your scenario?
> More detailed informaiton, I believe, will make us closer to the
resolution.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
|||What exactly do you mean by "ANSI characters are corrupted"? Have you tried
using oSql instead? oSql replaces iSql in 2000.
Andrew J. Kelly SQL MVP
"GMG" <nospam@.nospam.com> wrote in message
news:%23rbzxafrFHA.2228@.TK2MSFTNGP10.phx.gbl...
>I am automating a number of scripts to be run via ISQL, but I have found
> particular ANSI characters are corrupted. When running ISQLW via the
> command
> line everything is fine, but it outputs to file which is not ideal I would
> the output summary to display to the DOS screen.
> "Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
> news:WjTmruQrFHA.3532@.TK2MSFTNGXA01.phx.gbl...
> resolution.
> rights.
>
|||Hi GMG,
Thanks for the follow up.
I am also a little bit confused with "ANSI characters are corrupted". I
understood it was some characters will not be displayed correctly. If I
have misunderstood your concern, please feel free to point it out.
I am afraid we may not have a better way doing this directly. If you want
to get the output from file, you could generate a batch and output the file
after execute the isqlw in your scenario. You could use DOS command type
like this: type [driver:][filepath][filename]
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||I am sorry I was not very clear in my explanation.
I was able to solve the issue by going to 'Client Network Utility' - 'DB
Library Options' tab and disabling 'Automatic ANSI to OEM conversion'.
The ANSI characters are now correct when using ISQL to run my scripts.
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:n%23tA9MesFHA.3604@.TK2MSFTNGXA01.phx.gbl...
> Hi GMG,
> Thanks for the follow up.
> I am also a little bit confused with "ANSI characters are corrupted". I
> understood it was some characters will not be displayed correctly. If I
> have misunderstood your concern, please feel free to point it out.
> I am afraid we may not have a better way doing this directly. If you want
> to get the output from file, you could generate a batch and output the
file
> after execute the isqlw in your scenario. You could use DOS command type
> like this: type [driver:][filepath][filename]
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
|||Hi GMG,
Thanks for the update and it's great to know it was resolved.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
than file. How can I do this ?
Hi GMG,
Thanks for your post.
From you descriptions, I understood your ISQLW command line will
automatically output to a file instead of screen.
However, ISQLW will launch Query Analyzer and osql is the command line for
SQL Server. Both QA and osql will defaultly output to screen instead of
files. Would you please show me more detailed steps about your scenario?
More detailed informaiton, I believe, will make us closer to the resolution.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||I am automating a number of scripts to be run via ISQL, but I have found
particular ANSI characters are corrupted. When running ISQLW via the command
line everything is fine, but it outputs to file which is not ideal I would
the output summary to display to the DOS screen.
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:WjTmruQrFHA.3532@.TK2MSFTNGXA01.phx.gbl...
> Hi GMG,
> Thanks for your post.
> From you descriptions, I understood your ISQLW command line will
> automatically output to a file instead of screen.
> However, ISQLW will launch Query Analyzer and osql is the command line for
> SQL Server. Both QA and osql will defaultly output to screen instead of
> files. Would you please show me more detailed steps about your scenario?
> More detailed informaiton, I believe, will make us closer to the
resolution.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
|||What exactly do you mean by "ANSI characters are corrupted"? Have you tried
using oSql instead? oSql replaces iSql in 2000.
Andrew J. Kelly SQL MVP
"GMG" <nospam@.nospam.com> wrote in message
news:%23rbzxafrFHA.2228@.TK2MSFTNGP10.phx.gbl...
>I am automating a number of scripts to be run via ISQL, but I have found
> particular ANSI characters are corrupted. When running ISQLW via the
> command
> line everything is fine, but it outputs to file which is not ideal I would
> the output summary to display to the DOS screen.
> "Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
> news:WjTmruQrFHA.3532@.TK2MSFTNGXA01.phx.gbl...
> resolution.
> rights.
>
|||Hi GMG,
Thanks for the follow up.
I am also a little bit confused with "ANSI characters are corrupted". I
understood it was some characters will not be displayed correctly. If I
have misunderstood your concern, please feel free to point it out.
I am afraid we may not have a better way doing this directly. If you want
to get the output from file, you could generate a batch and output the file
after execute the isqlw in your scenario. You could use DOS command type
like this: type [driver:][filepath][filename]
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||I am sorry I was not very clear in my explanation.
I was able to solve the issue by going to 'Client Network Utility' - 'DB
Library Options' tab and disabling 'Automatic ANSI to OEM conversion'.
The ANSI characters are now correct when using ISQL to run my scripts.
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:n%23tA9MesFHA.3604@.TK2MSFTNGXA01.phx.gbl...
> Hi GMG,
> Thanks for the follow up.
> I am also a little bit confused with "ANSI characters are corrupted". I
> understood it was some characters will not be displayed correctly. If I
> have misunderstood your concern, please feel free to point it out.
> I am afraid we may not have a better way doing this directly. If you want
> to get the output from file, you could generate a batch and output the
file
> after execute the isqlw in your scenario. You could use DOS command type
> like this: type [driver:][filepath][filename]
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
|||Hi GMG,
Thanks for the update and it's great to know it was resolved.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
isqlw - SQL Query Analyzer recently used files list
Does anyone know of a tweak to increase the number of files that isqlw will
remember? 10 would be great...
David
Collaborative Data Services, FHCRC wrote:
> Does anyone know of a tweak to increase the number of files that
> isqlw will remember? 10 would be great...
> David
I don't think it's possible. Looking at the registry access by QA, it
appears it's looking for a fixed list of 5 files. I added a 6th and it
didn't read or look for it. I can't see any other registry setting that
identity the number of files to look for.
David Gugick
Imceda Software
www.imceda.com
|||I've tried a number of things in the past but nothing seems to work, I'm
pretty sure you're stuck with it.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Collaborative Data Services, FHCRC"
<CollaborativeDataServicesFHCRC@.discussions.micros oft.com> wrote in message
news:C68587DD-938E-42EE-B5F8-4F5B709E391C@.microsoft.com...
> Does anyone know of a tweak to increase the number of files that isqlw
> will
> remember? 10 would be great...
> David
|||I also agree with this.
Thanks
Hari
"Collaborative Data Services, FHCRC"
<CollaborativeDataServicesFHCRC@.discussions.micros oft.com> wrote in message
news:C68587DD-938E-42EE-B5F8-4F5B709E391C@.microsoft.com...
> Does anyone know of a tweak to increase the number of files that isqlw
> will
> remember? 10 would be great...
> David
remember? 10 would be great...
David
Collaborative Data Services, FHCRC wrote:
> Does anyone know of a tweak to increase the number of files that
> isqlw will remember? 10 would be great...
> David
I don't think it's possible. Looking at the registry access by QA, it
appears it's looking for a fixed list of 5 files. I added a 6th and it
didn't read or look for it. I can't see any other registry setting that
identity the number of files to look for.
David Gugick
Imceda Software
www.imceda.com
|||I've tried a number of things in the past but nothing seems to work, I'm
pretty sure you're stuck with it.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Collaborative Data Services, FHCRC"
<CollaborativeDataServicesFHCRC@.discussions.micros oft.com> wrote in message
news:C68587DD-938E-42EE-B5F8-4F5B709E391C@.microsoft.com...
> Does anyone know of a tweak to increase the number of files that isqlw
> will
> remember? 10 would be great...
> David
|||I also agree with this.
Thanks
Hari
"Collaborative Data Services, FHCRC"
<CollaborativeDataServicesFHCRC@.discussions.micros oft.com> wrote in message
news:C68587DD-938E-42EE-B5F8-4F5B709E391C@.microsoft.com...
> Does anyone know of a tweak to increase the number of files that isqlw
> will
> remember? 10 would be great...
> David
Subscribe to:
Posts (Atom)