Thanks for sharing your ideas.
I am not familiar with the :r SQL inclusion command (yet). Your approach seems indeed rather straightforward. I was personally thinking along a different path, but haven't been able to test my findings yet. The idea I had was to work through patches using
installer's default methodology to manage versions. I'll try to come up with a simple example in the next days and share it with you. Would certainly be interested to collaborate on some demos.
My idea on multiple databases is a little different. I understand you can create as many component elements as necessary (even if they all contain the same scripts). What I would like to realize is different. A user should be able to use the installer for
either creating a new database or upgrading an existing database. Upon a first install (NOT Installed), the user would only be able to create a new database. Next time however, the UI would ask what the user would like to do (create new or change existing).
So, I basically do not know upfront how many databases to create (and therefore cannot have multiple components doing the same thing). I have read some stuff about instance transforms, but am not sure this is the right way to go. I'll have to check further
No, that was not my question. I just want to list DATABASES on the selected server (not instances on a server). It is properly due to my (still) limited knowledge of Wix that I do not know how to include these in a combobox. Getting the results from the
server would be as easy as a 'select * from sys.databases'.