I think i have to dive into ORM and Hybernate sometime. My old fashioned way how to update a database might reached the end of its lifecycle
Okay, i know now, that an SQL-script is not an option. Could it be made possible to run updates via an URL? If yes, this would help very much: I can use Wget calling the URL with my Software Managment Solution.
Typo3 has interesting feature for enterprise business: They offer a centralized installation of the core code. If an update is needed, you only have to update once.
I donât see why you cant run a tool like Red Gate SQL, that will compare the production or staging with your development server DB. Which you can the script the differences into a SQL script. Which you can then use to update the production database.
Is there some part of this that is not possible with your setup?
I am assuming as part of your deployment you have scripts that update the source code, so why canât you use this tool to do the same for your SQL?
I agree that you should be able to get good mileage out of a tool like Red Gate SQL Compare and Data Compare, however it wonât cover all possible scenarios.
Consider a ContentBox update where Luis converted all Author names to uppercase. If you production environment has different authors than your development environment, Red Gate canât help you.
All updates are applied on the development server.
The data is changed on the development machine, Red Gate is then run to script the differences in both schema and data. These scripts are then used to migrate the production server changes.
It is true that Red Gate SQL could help. But Iâm but unsure, if this is the right way in terms of altering a database. With this, i would go an unsupported way, which i like to avoid.
On the other hand, those tools from Red Gate are really expensive.
Look at my example of a patch that backfills data. Assume you have a single author on dev now called âBOBâ (uppercased as part of the update) and a single author on production called âJohnâ (who needs to be uppercased). How would Red Gate help you there? It canât. All it can do is tell you that you have different data in both the dev and production tables. The best it can do is insert BOB on production and delete âJohnâ which isnât what you want. In order to upper case âJohnâ, you would actually have to execute a script on production (or run the update) to modify the data.
Imagine another scenario where your security rules are different between dev and production. Using Red Gate Data Compare to synch up the tables would be disastrous as you just now put your development security rules on production.
Not sure how your databases are setup, whether you can access them remotely or NOT. But you could look into the management tools that MS SQL server for replication as well.
Letâs continue this dream of enterprise management
WordPress offers a plugin (must be payed), which you can connect to all installed WordPress installations. You can see the versions of the installations and one mouse click starts the updates, if needed. This would be also great solution for ContentBox.
Hmm, sounds like an idea. However I have doubts about this, as long as it was 100% guaranteed to be secure it could be an option someone can write for ContentBox now.
We do have future plans to be able to register ContentBox installs with each other for pushing content and other things. Updating sounds like a good idea to build on that with.
100% guaranteed to be secure it could be an option someone can write for ContentBox
My idea: One ContentBox installation will be declared as the master site. On this site a plugin will offer an UI, UserID and passwod for a slave site.
On a slave site, also an plugin will tale care for a secure communication with the Master. e.g. the URL of the master site can be added.
Hi Luis, coming late to this thread but you asked earlier about a tool that can compare database differences and generate a script this tool does that.
