I'm currently building an MSI to install SQL Express and want to install as a new instance, not the default instance, and not into the SQLEXPRESS instance either.
I saw the package.xml for Express in my VS Studio install. How would I go about using this Or would I have to modify the MSI via Orca or something I hope not. Wouldn't have a clue where to start.
In short, regardless if there is already an SQL Express instance on the machine or not, I need to silently install a fresh new instance of the server engine only, no client tools except sqlcmd.exe
I have seen that MS would advise that everyone use the SQLEXPRESS instance but I don't agree with it. I don't want other application installs trampling over my server settings and I don't want to trample over others. For example, expose others to TCP\IP and CLR when they don't need it, and conversely others swithing them off in a shared server instance when I do need them.
Silent install new SQL Express instance via MSI
Brown_Jeff
Hi Allan,
The Package.xml stuff is about doing Click-Once installs with Visual Studio, if that's how you're doing your installation, modify it may be the way to go. You should also take a look at the command line options for the SQL Express installation package, using these allows you to configure many things about the SQL Express installation, including Instance Name. You can then wrap the installation of SQL Express in any other installer by providing the appropriate command line.
To your point of wanting your own copy of the server so as not to worry about other applications changing the settings of the server, that is certainly a choice you make for your application, but I offer a few counter points:
As I said, it's your choice in how you develop, but I'm not totally convinced that you're making the right choice for your customer.
Mike
KrishnaUNISYS
S'okay, got it figured out. Modifed the package.xml for SQL Express setting INSTANCENAME and commenting out the appropriate BypassIf already installed element. In the end I couldn't figure out how to install just the engine and sqlcmd.exe, ADDLOCAL didn't seem to cover it - all client tools or none - so allowed them all and modified the repair in my MSI to make sure all my configuration can be reset should someone muck around with SAC etc.
Now we've got a locked down instance only accessible via SQL logins generated on the fly, and via (local)\instance SSPI.
thames
Allen,
Did you get this to work
I am in need for the same implemention..
erik
Greg Van Mullem
Ok now i am not sure which way to go since I found this..
---------------------------
Note A SQL Server Express wrapper cannot be MSI-based because Windows Installer does not support multiple instantiation of the Windows Installer service.
---------------------------
I need to find a way to get the client user to downloand and install this sqlExpress with out seeing or having to answer and hard tech questions..
MauriceSibrandi
Allen,
Were you ever able to get this to work
Erik
James A P
Mike,
I am in need for someone to point me in the right direction. I have spent about three days trying to get a handle on how i am going to get this data to the clients desktops..
My first choice was click once then i found out that it is to light for my scenario ( however; i am really looking for to using this ClickOnce later on.... )
What i scenario that I need to solve is this.
Clients have a 5- 10 table set up on at a website that lets them add and update their products and company info..
Clients have a desktop app that almost mirrors the web environment but now they can work on the website away from the web (disconnected environment)
I need to install the sqlExpress when the user downloads the windows application for the first time..
My question to you is.... What is the absolute minimum command line args that i can set in the <<< template.ini >>> file ....( " In other words i just need what ever it takes to get and store the data; and run the sprocs; " ) $$$ the less the user finds on their computer the better.... And also; can i just store sqlExpress in my Application dir and not the C:\Program Files\Microsoft SQL Server **My problem is that i need so tech input but with out the tech language; So i can actually go back and reread and know what it is that i really need...
I hope that i am making since..
Can you at least point me in the right direction.... Reading is not the problem is just need a little help understanding what it is that I REALLY need to do vs. what it is that I THIINK I need to do..
Thanks a lot
Erik