Re: Unattended installation for SQL Server 2000

Just so that we are on the same page, the 2000 JDBC driver supports only Sql
Server 2000, but the 2005 JDBC driver supports both Sql Server 2000 _and_
Sql Server 2005. Moving to the new driver would not mean that you have to
use the newer server. I wish I could say that you should just be able to
swap the two drivers but this is just not the case, there are quite a few
differences in behavior between the drivers since they are completely
different code bases. Even so for a new project I would still recommend
taking the hit of going with the new driver as a better option in terms of
performance and supportability.

As far as redistribution being "not a problem" for internal
redistribution... I am not even going to claim to know what I am talking
about here, I try to stay as far away from these topics as possible. I would
recommend you have your legal department take a look at the license that
ships with the 2000 JDBC driver, this is a third party license that we have
to comply with and it explicitly restricts us from allowing redistribution.

I do know that there are no redistribution problems (internal or external)
with the 2005 driver.

--
Angel Saenz-Badillos [MS] Data Programmability
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.
I am now blogging: http://blogs.msdn.com/angelsb/




<WombatDeath@xxxxxxxxx> wrote in message
news:1151673135.904817.57990@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thank you for your response, Angel.

"If you are asking about installing the JDBC 2000 driver automatically"

Yes, that's the question. A bit of background: I want to install a web
application onto lots of laptops (the salesforce of the company I work
for). Most components of the application (SQL Server (personal
edition), etc) can be installed without user interaction, and I'm
trying to find a way to do the same with the JDBC driver. The ideal end
result is a CD from which I can install all components by executing a
batch file, without having to click 'Next' a million times.

I'm assuming that redistribution isn't a problem here since the users
are all internal employees of my company - we're not selling this
application.

Using SQL Server 2005 would be nice for several reasons, but at this
stage in the project it's unfortunately not practical to switch now.


Angel Saenz-Badillos[MS] wrote:
I am not sure I understood the question correctly. If you are asking
about
installing the JDBC 2000 driver automatically please note that this
driver
does not have a redistributable license, each instance should be
downloaded
from Microsoft directly.

You can apply for a redistributable license for the JDBC 2005 driver at
http://msdn.microsoft.com/data/ref/jdbc/redist/default.aspx. Once this is
done "installing" this driver is as simple as copying the jar and dlls
you
require to the directories you wish to use, if you are shipping an actual
application you can even make the driver part of your redistributable.

One of the main reasons behind starting over with the 2005 JDBC driver
was
to be able to offer this license.

--
Angel Saenz-Badillos [MS] Data Programmability
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.
I am now blogging: http://blogs.msdn.com/angelsb/




<WombatDeath@xxxxxxxxx> wrote in message
news:1151589628.851821.11400@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,

I'd like to perform several unattended installations of the JDBC driver
for SQL Server 2000 (Personal Edition). Is there a simple way of doing
this, perhaps similar to the manner in which SQL Server itself can be
installed by tweaking a default script file?

Failing that, if anyone else has created their own script for
installing the JDBC driver I would be very grateful if you would share
it.

Thanks in advance!




.

Relevant Pages
Loading