isql.exe

16 Oct 2007 10:20 AM

Ashwathdama

Hi,
In our organisation we are migrating from SQL Server 2000 to 2005.
we have more number of dos based batch files created using isql.exe
file. Since sql server 2005 doesn't support isql.exe those batch files
are not working. equalent one available is sqlcmd but if we have to
migrate then around 720 batch files needs to be migrated and tested
and some of our clients may also have old batch file whihc may cause
problem.

is isql.exe re-distributable ?

Cheers
Rajesh

16 Oct 2007 12:34 PM

Russell Fields

Rajesh,

It is not a matter of whether isql.exe is redistributeable, but of whether
it works with 2005. The Books Online say "not supported in SQL Server
2005".

I just ran isql and it worked for a simple query, but I have some processes
that used isql that no longer worked once I upgraded my servers to 2005.
What I did is globally change the "isql" references to "osql". This is not
as up-to-date as sqlcmd, but it worked for me.

FWIW,
RLF

<Ashwathd***@gmail.com> wrote in message
Show quote

news:1192530039.044572.40580@i38g2000prf.googlegroups.com...
> Hi,
> In our organisation we are migrating from SQL Server 2000 to 2005.
> we have more number of dos based batch files created using isql.exe
> file. Since sql server 2005 doesn't support isql.exe those batch files
> are not working. equalent one available is sqlcmd but if we have to
> migrate then around 720 batch files needs to be migrated and tested
> and some of our clients may also have old batch file whihc may cause
> problem.
>
> is isql.exe re-distributable ?
>
>
> Cheers
> Rajesh
>

16 Oct 2007 10:08 PM

Erland Sommarskog

(Ashwathd***@gmail.com) writes:

> In our organisation we are migrating from SQL Server 2000 to 2005.
> we have more number of dos based batch files created using isql.exe
> file. Since sql server 2005 doesn't support isql.exe those batch files
> are not working. equalent one available is sqlcmd but if we have to
> migrate then around 720 batch files needs to be migrated and tested
> and some of our clients may also have old batch file whihc may cause
> problem.
>
> is isql.exe re-distributable ?

Not only would you have to redistribute ISQL, you will also have to
redistribute NTWDBLIB.DLL too. What you need legally to do this, you
need to ask your local Microsoft representative. (This here is a forum
for technical people, licensing is for lawyers.)

But I would definitely recommend that you bite the bullet. Next year
there will be a new version of SQL Server, SQL 2008. That version will
support connections from DB-Library. But some years even later, there
will yet a new version of SQL Server, and that version will *not* accept
connections from DB-Library and thus not from ISQL.

Also, with ISQL you run with non-standard settings (unless you include
SET commands in all your scripts), which causes commands to fail or
perform badly, if there are certain features involved like indexed views,
XQuery, distributed queries.

So you really need to plan how to deal with those 720 batch files.

--
Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

17 Oct 2007 7:11 AM

Ashwathdama

On Oct 17, 3:08 am, Erland Sommarskog <esq***@sommarskog.se> wrote:
Show quote

> (Ashwathd***@gmail.com) writes:
> > In our organisation we are migrating from SQL Server 2000 to 2005.
> > we have more number of dos based batch files created using isql.exe
> > file. Since sql server 2005 doesn't support isql.exe those batch files
> > are not working. equalent one available is sqlcmd but if we have to
> > migrate then around 720 batch files needs to be migrated and tested
> > and some of our clients may also have old batch file whihc may cause
> > problem.
>
> > is isql.exe re-distributable ?
>
> Not only would you have to redistribute ISQL, you will also have to
> redistribute NTWDBLIB.DLL too. What you need legally to do this, you
> need to ask your local Microsoft representative. (This here is a forum
> for technical people, licensing is for lawyers.)
>
> But I would definitely recommend that you bite the bullet. Next year
> there will be a new version of SQL Server, SQL 2008. That version will
> support connections from DB-Library. But some years even later, there
> will yet a new version of SQL Server, and that version will *not* accept
> connections from DB-Library and thus not from ISQL.
>
> Also, with ISQL you run with non-standard settings (unless you include
> SET commands in all your scripts), which causes commands to fail or
> perform badly, if there are certain features involved like indexed views,
> XQuery, distributed queries.
>
> So you really need to plan how to deal with those 720 batch files.
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
> Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Thank you !!!. I will just check it up what is possible for me to go
with that.

Cheers
Rajesh