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

ISQL: Msg 170, Level 15, State 1, Line 1 Line 1: Incorrect syntax near ' '

G'day everyone
That's a space between the ticks.
It's all part of a longer script but seeing as the failure occurs on
line 1
if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[config]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [dbo].[config]
GO
That's three lines only. Does it matter that they're in Unicode?
Any ideas?
Kind regards,
Bruce M. Axtens
Software Engineer
Strapper TechnologiesI pasted that code into a .sql file and ran it through isql.exe and it executed without errors. What
version of SQL Server to you connect to?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"axtens" <Bruce.Axtens@.gmail.com> wrote in message
news:1162976105.388119.97910@.b28g2000cwb.googlegroups.com...
> G'day everyone
> That's a space between the ticks.
> It's all part of a longer script but seeing as the failure occurs on
> line 1
> if exists (select * from dbo.sysobjects where id => object_id(N'[dbo].[config]') and OBJECTPROPERTY(id, N'IsUserTable') => 1)
> drop table [dbo].[config]
> GO
> That's three lines only. Does it matter that they're in Unicode?
> Any ideas?
> Kind regards,
> Bruce M. Axtens
> Software Engineer
> Strapper Technologies
>|||Tibor,
Thanks for your reply. I found out from another group that the line
count is reset each time ISQL executes a "GO" statement, so the
offending line could have been anywhere in a 123 line file.
What I ended up doing was creating two scripts from the original: one
to do the "DROP"s and the other to do the "CREATE"s.
Thanks for your time.
Kind regards,
Bruce M. Axtens
Software Engineer
Strapper Technologies

ISQL/W - SQL graphical query tool

hi, i have an error when i open the query analizer and press F1 to use the
help, the error that is displayed to say :
ISQL w - graphical query tool
ISQL/w - SQL graphical query tool to detected a throuble and had to close
...
and i can not use the help, may someone help me, please?
thanks
JJ_ wrote:
> hi, i have an error when i open the query analizer and press F1 to
> use the help, the error that is displayed to say :
> ISQL w - graphical query tool
> ISQL/w - SQL graphical query tool to detected a throuble and had to
> close ...
>
> and i can not use the help, may someone help me, please?
>
> thanks
Install the SQL Server Service Pack 3a on the client PC and see if that
helps.
David G.
|||David,
I Install the SQL Server Service Pack 3a on my PC and nothing, the error is
displayed again when I want to raise the help to press F1, do you have
another idea, please?
thanks
"David G." wrote:

> JJ_ wrote:
> Install the SQL Server Service Pack 3a on the client PC and see if that
> helps.
> --
> David G.
>
|||When I start QA and press F1, this is the help file that opens:
C:\Program Files\Microsoft SQL Server\80\Tools\Books\startsql.chi
Do you have this file?
David Gugick
Imceda Software
www.imceda.com

ISQL vs OSQL

Hello
I use SQL Server 2000. I always use Query Analyzer to run scripts, so I don't know OSQL and ISQL. I have some questions.
1. What is difference between ISQL and OSQL?
2. Which one is better?( this question is silly.)
3. What are pros and cons?
4. Which one do most people use?
5. What is a reason to use either of the tools rather than Query Analyzer? (if you use them)
6. Are there any documents (or manuals) about OSQL and ISQL?
7. Any comments?
Thanks in advance.
Do.
Message posted via http://www.sqlmonster.com
Do Park via SQLMonster.com wrote:
> Hello
> I use SQL Server 2000. I always use Query Analyzer to run scripts, so
> I don't know OSQL and ISQL. I have some questions.
> 1. What is difference between ISQL and OSQL?
> 2. Which one is better?( this question is silly.)
> 3. What are pros and cons?
> 4. Which one do most people use?
> 5. What is a reason to use either of the tools rather than Query
> Analyzer? (if you use them)
> 6. Are there any documents (or manuals) about OSQL and ISQL?
> 7. Any comments?
> Thanks in advance.
> Do.
ISQL uses dbLib as its mechanism for connecting to the server and acts
as a SQL Server 6.5 client when connected (legacy application). So you
may not have access to all SQL Server 2000 features. ISQL does not
support unicode.
OSQL uses ODBC as its mechanism for connecting to the server and
supports SQL Server 2000 fully and is unicode compliant.
These are both command-line utilities and are useful when you have to
execute a batch against a database or wish to quickly extract data from
a database using a query.
Use OSQL.
You can read all about them in the help file...
David Gugick
Imceda Software
www.imceda.com

isql query output issue

Hi
I am planning to get a report out from isql using command
c:\> isql -Usa -P -d master -i c:\l.sql -o c:\op.lst
c:\> type l.sql
select * from sysobjects;
In op.lst I see 3 blank lines for every line of the output. How to avoid this.
I tried by creating a job to avoid this but there I found the first line of
the output says this
Job 'TSQL_Job_1' : Step 1, 'Step 1' : Began Executing 2005-02-14 14:54:16
---------
Please share with me how to avoid this unncessary data in report.
Thanks
Mangesh
Hi
Thee are 3 blank lines, but that is the spacing for the column 'name'. It is
of datatype sysname, char(128).
Regards
Mike
"Mangesh Deshpande" wrote:

> Hi
> I am planning to get a report out from isql using command
> c:\> isql -Usa -P -d master -i c:\l.sql -o c:\op.lst
> c:\> type l.sql
> select * from sysobjects;
> In op.lst I see 3 blank lines for every line of the output. How to avoid this.
> I tried by creating a job to avoid this but there I found the first line of
> the output says this
>
> Job 'TSQL_Job_1' : Step 1, 'Step 1' : Began Executing 2005-02-14 14:54:16
>
>
> ---------
>
> Please share with me how to avoid this unncessary data in report.
> Thanks
> Mangesh
|||Hi
Thanks for the reply. How do we get rid of this space. Is there a way to
this?
"Mangesh Deshpande" wrote:

> Hi
> I am planning to get a report out from isql using command
> c:\> isql -Usa -P -d master -i c:\l.sql -o c:\op.lst
> c:\> type l.sql
> select * from sysobjects;
> In op.lst I see 3 blank lines for every line of the output. How to avoid this.
> I tried by creating a job to avoid this but there I found the first line of
> the output says this
>
> Job 'TSQL_Job_1' : Step 1, 'Step 1' : Began Executing 2005-02-14 14:54:16
>
>
> ---------
>
> Please share with me how to avoid this unncessary data in report.
> Thanks
> Mangesh
|||Hi
Don't use SELECT *, it is a bad practice. Rather specify each column.
RTRIM will trim trailing spaces.
SELECT RTRIM([Name]) AS MyName, ........
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message news:AA4199DE-C15A-4507-BB15-C1BD1D835F3B@.microsoft.com...[vbcol=seagreen]
> Hi
> Thanks for the reply. How do we get rid of this space. Is there a way to
> this?
> "Mangesh Deshpande" wrote:
this.[vbcol=seagreen]
of[vbcol=seagreen]
14:54:16
> ----
---[vbcol=seagreen]

isql query output issue

Hi
I am planning to get a report out from isql using command
c:\> isql -Usa -P -d master -i c:\l.sql -o c:\op.lst
c:\> type l.sql
select * from sysobjects;
In op.lst I see 3 blank lines for every line of the output. How to avoid thi
s.
I tried by creating a job to avoid this but there I found the first line of
the output says this
Job 'TSQL_Job_1' : Step 1, 'Step 1' : Began Executing 2005-02-14 14:54:16
----
----
---
Please share with me how to avoid this unncessary data in report.
Thanks
MangeshHi
Thee are 3 blank lines, but that is the spacing for the column 'name'. It is
of datatype sysname, char(128).
Regards
Mike
"Mangesh Deshpande" wrote:

> Hi
> I am planning to get a report out from isql using command
> c:\> isql -Usa -P -d master -i c:\l.sql -o c:\op.lst
> c:\> type l.sql
> select * from sysobjects;
> In op.lst I see 3 blank lines for every line of the output. How to avoid t
his.
> I tried by creating a job to avoid this but there I found the first line o
f
> the output says this
>
> Job 'TSQL_Job_1' : Step 1, 'Step 1' : Began Executing 2005-02-14 14:54:16
>
>
> ----
----
---
>
> Please share with me how to avoid this unncessary data in report.
> Thanks
> Mangesh|||Hi
Thanks for the reply. How do we get rid of this space. Is there a way to
this?
"Mangesh Deshpande" wrote:

> Hi
> I am planning to get a report out from isql using command
> c:\> isql -Usa -P -d master -i c:\l.sql -o c:\op.lst
> c:\> type l.sql
> select * from sysobjects;
> In op.lst I see 3 blank lines for every line of the output. How to avoid t
his.
> I tried by creating a job to avoid this but there I found the first line o
f
> the output says this
>
> Job 'TSQL_Job_1' : Step 1, 'Step 1' : Began Executing 2005-02-14 14:54:16
>
>
> ----
----
---
>
> Please share with me how to avoid this unncessary data in report.
> Thanks
> Mangesh|||Hi
Don't use SELECT *, it is a bad practice. Rather specify each column.
RTRIM will trim trailing spaces.
SELECT RTRIM([Name]) AS MyName, ........
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message news:AA4199DE-C15A-4507-BB15-C1BD1D835F3B@.microsoft.com...
> Hi
> Thanks for the reply. How do we get rid of this space. Is there a way to
> this?
> "Mangesh Deshpande" wrote:
>
this.[vbcol=seagreen]
of[vbcol=seagreen]
14:54:16[vbcol=seagreen]
> ----
----
---[vbcol=seagreen]

isql query output issue

Hi
I am planning to get a report out from isql using command
c:\> isql -Usa -P -d master -i c:\l.sql -o c:\op.lst
c:\> type l.sql
select * from sysobjects;
In op.lst I see 3 blank lines for every line of the output. How to avoid this.
I tried by creating a job to avoid this but there I found the first line of
the output says this
Job 'TSQL_Job_1' : Step 1, 'Step 1' : Began Executing 2005-02-14 14:54:16
---------
Please share with me how to avoid this unncessary data in report.
Thanks
MangeshHi
Thee are 3 blank lines, but that is the spacing for the column 'name'. It is
of datatype sysname, char(128).
Regards
Mike
"Mangesh Deshpande" wrote:
> Hi
> I am planning to get a report out from isql using command
> c:\> isql -Usa -P -d master -i c:\l.sql -o c:\op.lst
> c:\> type l.sql
> select * from sysobjects;
> In op.lst I see 3 blank lines for every line of the output. How to avoid this.
> I tried by creating a job to avoid this but there I found the first line of
> the output says this
>
> Job 'TSQL_Job_1' : Step 1, 'Step 1' : Began Executing 2005-02-14 14:54:16
>
>
> ---------
>
> Please share with me how to avoid this unncessary data in report.
> Thanks
> Mangesh|||Hi
Thanks for the reply. How do we get rid of this space. Is there a way to
this?
"Mangesh Deshpande" wrote:
> Hi
> I am planning to get a report out from isql using command
> c:\> isql -Usa -P -d master -i c:\l.sql -o c:\op.lst
> c:\> type l.sql
> select * from sysobjects;
> In op.lst I see 3 blank lines for every line of the output. How to avoid this.
> I tried by creating a job to avoid this but there I found the first line of
> the output says this
>
> Job 'TSQL_Job_1' : Step 1, 'Step 1' : Began Executing 2005-02-14 14:54:16
>
>
> ---------
>
> Please share with me how to avoid this unncessary data in report.
> Thanks
> Mangesh|||Hi
Don't use SELECT *, it is a bad practice. Rather specify each column.
RTRIM will trim trailing spaces.
SELECT RTRIM([Name]) AS MyName, ........
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message news:AA4199DE-C15A-4507-BB15-C1BD1D835F3B@.microsoft.com...
> Hi
> Thanks for the reply. How do we get rid of this space. Is there a way to
> this?
> "Mangesh Deshpande" wrote:
> > Hi
> >
> > I am planning to get a report out from isql using command
> > c:\> isql -Usa -P -d master -i c:\l.sql -o c:\op.lst
> > c:\> type l.sql
> > select * from sysobjects;
> >
> > In op.lst I see 3 blank lines for every line of the output. How to avoid
this.
> >
> > I tried by creating a job to avoid this but there I found the first line
of
> > the output says this
> >
> >
> > Job 'TSQL_Job_1' : Step 1, 'Step 1' : Began Executing 2005-02-14
14:54:16
> >
> >
> >
> >
> ----
----
---
> >
> >
> > Please share with me how to avoid this unncessary data in report.
> >
> > Thanks
> > Mangesh

ISQL query fails after reboot

Good morning we are having a wierd issue with our Windows 2003 server and SQ
L
2000 sp4 server. From the client side we use isql queries. When we reboot
the server the isql queries that are larger then 512 bytes will fail from
both the client or from the sql server itself smaller ones will work. Query
analyzer works perfectly. The strange part is if we run any query in either
query analyzer or using isql then restart the services everything works. We
also have another server which appears to be identical and everything works
with no issues. If anyone can point me in the right direction to
troubleshoot this issue it would be greatly appreciated.
Richard TracyHave you tried using OSQL instead of ISQL?
In terms of why you are having problems, that's hard to say
without knowing what error message you receive when running
the queries that fail. As a guess, it sounds like you could
be running into issues related to ISQL and the packet size.
Try using the -a switch and increase the default packet
size.
-Sue
On Wed, 12 Apr 2006 07:50:02 -0700, Richard Tracy
<RichardTracy@.discussions.microsoft.com> wrote:

>Good morning we are having a wierd issue with our Windows 2003 server and S
QL
>2000 sp4 server. From the client side we use isql queries. When we reboot
>the server the isql queries that are larger then 512 bytes will fail from
>both the client or from the sql server itself smaller ones will work. Quer
y
>analyzer works perfectly. The strange part is if we run any query in eithe
r
>query analyzer or using isql then restart the services everything works. W
e
>also have another server which appears to be identical and everything works
>with no issues. If anyone can point me in the right direction to
>troubleshoot this issue it would be greatly appreciated.
>Richard Tracy|||We have tried using the -a with no success the error we get is a network
error even if we run it on the localhost. We have also uninstalled sql
server and tried it on a plain vanilla sql server with no success. Any idea
s
of how to troubleshoot this would be greatly appreciated
Thank you
"Sue Hoegemeier" wrote:

> Have you tried using OSQL instead of ISQL?
> In terms of why you are having problems, that's hard to say
> without knowing what error message you receive when running
> the queries that fail. As a guess, it sounds like you could
> be running into issues related to ISQL and the packet size.
> Try using the -a switch and increase the default packet
> size.
> -Sue
> On Wed, 12 Apr 2006 07:50:02 -0700, Richard Tracy
> <RichardTracy@.discussions.microsoft.com> wrote:
>
>|||You really have to look at the exact full error messages and
the error number. You can try googling on those or try
posting with the full information. Connectivity issues are
generally difficult to troubleshoot via newsgroups. If you
want to do that, you need to post a lot of details, full
error messages, configurations, exact steps to reproduce,
etc. Even then, it can be difficult via newsgroups.
-Sue
On Thu, 13 Apr 2006 23:18:02 -0700, Richard Tracy
<RichardTracy@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>We have tried using the -a with no success the error we get is a network
>error even if we run it on the localhost. We have also uninstalled sql
>server and tried it on a plain vanilla sql server with no success. Any ide
as
>of how to troubleshoot this would be greatly appreciated
>Thank you
>"Sue Hoegemeier" wrote:
>|||Thank you for your help Sue. We found what the issue was, we found it was
being caused by an application called NCS (Native Command Substitution. It
is installed with lightspeed which was created by imceda software which has
been bought by quest software. We removed this software and it has worked
without an issue. Again thak you very much for your help
"Sue Hoegemeier" wrote:

> You really have to look at the exact full error messages and
> the error number. You can try googling on those or try
> posting with the full information. Connectivity issues are
> generally difficult to troubleshoot via newsgroups. If you
> want to do that, you need to post a lot of details, full
> error messages, configurations, exact steps to reproduce,
> etc. Even then, it can be difficult via newsgroups.
> -Sue
> On Thu, 13 Apr 2006 23:18:02 -0700, Richard Tracy
> <RichardTracy@.discussions.microsoft.com> wrote:
>
>|||That's interesting one ...thanks for posting back.
-Sue
On Sun, 16 Apr 2006 14:01:02 -0700, Richard Tracy
<RichardTracy@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thank you for your help Sue. We found what the issue was, we found it was
>being caused by an application called NCS (Native Command Substitution. It
>is installed with lightspeed which was created by imceda software which has
>been bought by quest software. We removed this software and it has worked
>without an issue. Again thak you very much for your help
>"Sue Hoegemeier" wrote:
>

isql problem with null values

I am having a problem running a stored procedure using isql to launch the procedure.

My stored procedure contains a statement like:

select @.myvar = count(*) from mytable where mycolumn is null

when I run the procedure from query analyser a value is set in @.myvar showing the correct number of null values from mytable which is output to another table where I can see it.

Without making any changes, when I run the identical procedure using isql to execute the procedure @.myvar gets set to zero. The procedure cannot find the null values in mytable

I have tried setting ANSI_NULLS on and off inside the procedure but still get the same result.

Can someone please tell me what is going on, and how I might get isql to show me how many null values exist in the table?I don't seems to have anyproblem with this

USE Northwind
GO

CREATE TABLE myTable99(Col1 int)
GO

INSERT INTO myTable99(Col1)
SELECT 1 UNION ALL
SELECT 2 UNION ALL
SELECT 3 UNION ALL
SELECT null UNION ALL
SELECT null UNION ALL
SELECT null
GO

CREATE PROC mySproc99 @.Rows int OUTPUT AS
SELECT @.Rows = COUNT(*) FROM myTable99 WHERE Col1 IS NULL
GO

DECLARE @.Rows int
EXEC mySproc99 @.Rows OUTPUT
SELECT @.Rows

DECLARE @.cmd varchar(8000), @.sql varchar(8000)
SELECT @.sql = 'DECLARE @.Rows int EXEC mySproc99 @.Rows OUTPUT SELECT @.Rows'
SELECT @.cmd = 'osql -U <username> -P <password> -S <servername> -d Northwind -Q "' + @.sql + '"'
EXEC master..xp_cmdshell @.cmd
GO

DROP PROC mySproc99
DROP TABLE myTable99
GO|||Which SQL Server are you running? If SQL 2000, which campatibility level?|||Brett,

Thanks for your reply, I'll try out your script tomorrow morning when I get into the office. And let you know the result.

The reason I'm confused, is I set up my script using osql and it worked fine on our test server, It didn't run at all on production, then I found that it did run if I changed osql to isql, but with the quirk noted. I'm sure it is something to do with the OLE DB config, but I am not sure where to start looking for differences. Also the osql version might work if I could get ODBC set up on production, but I'm not sure how to go about doing that.

Anyway, thanks again for all your help and I'd be grateful for any further suggestions.|||I don't have tons of experience with xp_cmdshell but my results from the example script above look pretty strange:

www.sullivanstreet.us/query.jpg