Installing MSDE

I have almost finished developing an application that uses MSDE. I want to
now deploy MSDE with my app. I have the original SQL Server 2000 CD that
contains the MSDE setup files.
I understand that there has been a major upgrade to MSDE 2000 and that I
should use some sevice pack files to install MSDE. Do I download this
service pack (sql2desk.exe?), extract the files in there and copy them over
the original files? Or do I need to install using the original CD and then
upgrade the installation with the service pack stuff?
TIA,
Paul
hi Paul,
"Paul McTeigue" <paul_mcteigue@.msn.com> ha scritto nel messaggio
news:ePVutaLIEHA.348@.tk2msftngp13.phx.gbl...
> I have almost finished developing an application that uses MSDE. I want to
> now deploy MSDE with my app. I have the original SQL Server 2000 CD that
> contains the MSDE setup files.
> I understand that there has been a major upgrade to MSDE 2000 and that I
> should use some sevice pack files to install MSDE. Do I download this
> service pack (sql2desk.exe?), extract the files in there and copy them
over
> the original files? Or do I need to install using the original CD and then
> upgrade the installation with the service pack stuff?
you only have to use and deploy the content of the new sql2desk.exe, updated
at service pack 3a level..
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql

Installation of Table Question

Hi,
I am developing an add on to a db application where I need to install a
couple of tables to an existing db. I am curious what others use for
installation. Do most developers use SQL scripts excuted by ossql command
in a batch file?
ThanksI find that to be the most effective way to deliver the package. However,
it's really coming down to personal preference. You can also deliver the
package by making an ado connection to the database and run your ddl against
the database.
-oj
"George" <george@.ny.com> wrote in message
news:OALHWKfoFHA.2916@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I am developing an add on to a db application where I need to install a
> couple of tables to an existing db. I am curious what others use for
> installation. Do most developers use SQL scripts excuted by ossql command
> in a batch file?
> Thanks
>|||That is the way I would do it. I find it reassuring as a dba to be able to
view queries that will be executed against the database. At least one
application I support does it like oj suggested and it makes me feel kind of
uneasy to run the rather frequent upgrade programs. I would probably like
to see the setup program launch the change script, if possible. I would use
OSQL to do it because it natively supports GO batch separators and it makes
writing code like this more natural, and OSQL gives you everything you need.
I guess the most important thing to ask is who will be using this upgrade?
Just your corporate user or is this a commercial application.
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"George" <george@.ny.com> wrote in message
news:OALHWKfoFHA.2916@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I am developing an add on to a db application where I need to install a
> couple of tables to an existing db. I am curious what others use for
> installation. Do most developers use SQL scripts excuted by ossql command
> in a batch file?
> Thanks
>