We currently install SQL Server 2005 Express silently during our installation, using the following switches
/qn ADDLOCAL=all REBOOT=ReallySuppress DISABLENETWORKPROTOCOLS=2 SQLAUTOSTART=1 SECURITYMODE=SQL SAPWD=123
We also attach a 2005-created database immediately after using the following command line (^ is a path concat operator in Installshield):
sqlcmd.exe -S .\\SQLEXPRESS -E -i \"" + svConfigPath ^ "SetupUapDB.sql\" -vmdfpath=\"" + svConfigPath ^ "UapCfg.mdf\" -vldfpath=\"" + svConfigPath ^ "UapCfg_log.ldf\" -o \"" + svConfigPath ^ "SqlCreateDB.txt\" -e
Note that we do not specify an instance name. We ran into a situation where someone had installed SQL Server 2008 on a box using a default instance name and our install then failed. I am considering 2 possible fixes, and have questions for both.
Fix #1: Specify an instance name. Ideally this would install SQL Server 2005 Express side by side with SQL Server 2008, create a unique instance name and we'd be good to go right? If yes, what is the accepted convention for specifying instance
Fix #2: Not sure if this is possible. Can we detect if SQL Server 2008 is on the box, and if yes, apply our 2005 database to it instead? In this case (tell me
View Complete Post