RunCommands problem in Setup.lst

Im trying to create a setup cd using office setup wizard. I want the setup to
install my MSDE SP3 at the end of the installation. So I've placed the
following command in the setup.lst under [RunCommands]
MSDERelA\setup.exe InstanceName="TaShel" SAPWD "sa" SecurityMode="SQL
MSDERelA is a folder on my setup cd containing the MSDE files.
I can use the same command to run it from the command prompt but the command
is not running during the setup process.
If anyone could shed some light on this problem of mine.
Thanks
Dorji
hi Dorji,
Dorji wrote:
> Im trying to create a setup cd using office setup wizard. I want the
> setup to install my MSDE SP3 at the end of the installation. So I've
> placed the following command in the setup.lst under [RunCommands]
I'm not prepared about office setup wizard... try asking in the Office ng
hyerarchy...
BTW...
MSDERelA\setup.exe InstanceName="TaShel" SAPWD "sa" SecurityMode="SQL
=
MSDERelA\setup.exe InstanceName="TaShel" SAPWD="sa" SecurityMode=SQL
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Run SQL Server 7.0 in Windows 2003

Dear all,
Lately, we bought a new server to replace existing old one. After
installation of SQL7, we followed to install the service pack 4 into it.
During the installation, we found SQL7 didn't support in 2003. And we
continued the process until it finished. Is there any problem on using SQL7
in windows server 2003? Since we have some application supported in SQL7
only, we have to keep using SQL7. Anyone know there's any impact using SQL7
in windows 2003? Please help
Best Rdgs
EllisIs there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
> Best Rdgs
> Ellis
>

Run querys after silent installtion SQL 2005 Express

Hi,

I'm looking for a solution to run querys (create databases ed) after a silent installation of SQL 2005 Express edition (example with a .sql file). So users can run a installation unattended with all databases installed and so on.

What I got is a document about how to run a silent installation (document " Using Command Prompt Options to install SQL Server Express") but this docs there's no solution how to run querys after the installation.

Thanks

Robert-Paul

I think you want to use sqlcmd.exe after installation. This really isn't a setup issue. You will probably get a better answer in either the Tools or DB Engine forums.|||

Moving this post to the new SQL Express forum. Hope they can answer your question.

-Jeffrey

|||

Hi Robert- Paul,

You should use SQLCmd to run .sql scripts after a silent installation. You can find more information about SQLCmd in Books Online, which you can either download or find online at http://msdn2.microsoft.com. In general, you can call SQLCmd the same way you'd call any command line tool with a command line something like this:

SQLCmd -E -S <machinename>\SQLEXPRESS -i C:\myscript.sql

Regards,

Mike Wachal - SQL Express team