I have to make installer that installs Postgresql before our application, makes database and execute some sql scripts against the database.
Now I'm using the Bootstrapper to install Postgresql and then our application and using Wix install sequence I execute SQL script that takes care of the rest.
I'm wondering if there is any way to do it without Bootstrapper? I've read about Wix SqlExtension but can't figure out if it's database independent or if I can install databese server with it...
The WiX SqlExtension is SqlServer specific. However, it shouldn't be that hard to plumb in a Postgresql layer underneath it. IIRC, the actual database calls are pretty abstracted away.
Also, a bootstrapper isn't the correct place to do static configuration either. If this is really configurable data then maybe an entirely separate app launched at the end of install makes sense. But if it's just creating databases, I'd put that in the MSI itself.
Related
There are several ways to upgrade from V8 what I read on several fora.
One of the methods is do exports of "main tables"
Which tables? And it only works good with smaller DB's.
And how big is big ? I have only Accounting , CRM, and Website modules on my Odoo 8 and I am self employed, not an enterprise.
I know that you can easily upgrade from 8 - > 10 .
If I use the OpenUpgrade software, does it make a new DB which can then be used with a new instance of Odoo with V12? Or does it migrate the complete instance db + software?
If I downgrade modules in V10, will the upgrade to V12 be easy. Or are there special tables written in the DB who can block the migration from V10 -> V12 ?
Migrations are tricky. The basic process will be:
Make a copy of your database and ship it to a separate environment
Run OpenUpgrade V9.0 with the --upgrade=all flag on the database
If you come across any errors, handle them individually by looking at the error and making the necessary changes to your modules
Once the upgrade completes, you can move forward and do the same for OpenUpgrade V10.0, V11.0 and V12.0
Copy your database back to production
My application uses postgreSQL Server for database operations. Am looking for a way to distribute postgreSQL windows binaries during installation of my application. As of my research i found we can distribute postgreSQL installer setup and make unattended installation on it. Is this a better way to do?.
Let me know the possible way to make out this work. Thanks.
I have to develop a software for CD. So, the project must run only in CD, without installing to computer. Installing and copying must be impossible from disc. The program is something like Language Learning program. Can I use .NET (c#) environment for such a program? And which databases can I use? (I heard about Firebird).
You could use firebird. However, you would need a connection to an external firebird server to be able to do physical operations on the data. Another solution would be to save the data on the client computer. For instance you could restore the database in a profile folder. It is unclear to me whether changes and learn progress should be saved.
We have a large application that has been developed over 15 years and in installed in 200+ client locations. The application currently consists of an Access database and a bunch of executable and report files located on a network share. A Setup.EXE file is run on each client machine (dlls are installed on the client) and then the client machines run the executables directly from the network share. During our upgrade procedure the new executable and report files are copied to the network share and that way each client gets the update immediately.
Our current installation program is very old and, among other things, it doesn't handle x64 so we are in the process of moving to a new deployment tool. At the same time we are migrating client Access databases to SQL Server. I am having difficulty finding a deployment tool to do what we require. Specifically we need the install/upgrade file to do the following:
It must be able to be run from a client machine on a network and copy the new executable and report files to the network share. That share could be a Linux box or a dumb storage device.
Accept a password before running the installation
Allow the user to select the network share as the location to copy the executables
It must NOT add anything to the client machine from where the package is run (Add/Remove Programs, registry, etc.)
Connect to a SQL Server database and run a script
The install/upgrade must be contained in a single, standalone .msi or .exe file. (no dependencies on dlls or frameworks other than those that come with Windows XP)
The file must be able to be run in one simple step. It is the end user that runs the upgrade without our support and without involvement from IT.
It looks like the closest thing to what I need is WiX but the problem there is that whenever the .msi file is run from a client, the client machine thinks that a program is being installed so it allows the client machine to uninstall the product, which is not acceptable.
If the product were written today it would certainly be architected differently but it currently is what it is and we can’t change that. Any help here would be greatly appreciated!
WiX is just a toolset built on top of Windows Installer technology. It makes many things easier and simpler as well as hides lots of Windows Installer weird features... But, it is still limited by Windows Installer, its underlying technology.
Your list of requirements made me think that Windows Installer is not the right technology to choose. I would assume that you'll spend more time on workarounds, than on functional code... But I have no experience with other installation technologies, so I'll leave those recommendations to others.
I'm working on building out a db2 database from scripts for build verification purposes.
Basically we have a set of db2 scripts that were extracted quite a while ago, and we'd like to build out these scripts into a db2 database, so that we can compare against production and make sure that they match.
Any thoughts on available tools? Or will we need to build this ourself?
thanks!
Sylvia
Update: Ideally this tool would have error trapping, logging, all that kind of stuff. Kind of like the Red Gate tools for SQL Server, but for DB2.
db2 comes with a command line processor.
db2 -tvf <filename>
You need to initialize your db2 environment first.