We had a discussion with our operations last week regarding to what MySQL server to install to develop a new application for one of our clients. Currently we use a 4.1.22 version and definitely we need a version higher than 5.0 as we are going to need to built views and maybe stored procedures. We are talking about Linux as OS.
As DBA my idea was to go for the last released version, which I think it is 5.1.31 but the guys from Operations said that they would like to stick with the 5.0.66 version because we already use that for another client. They want to keep a consistency in regards with the MySQL version we they install and we use at our company.
I have to admit that 5.0.66 already has the feature that we will need to implement this application and if an upgrade is anyway imminent for that client then why not use the last version of MySQL.
My question is how justified is that position to keep a consistency over the MySQL servers? What exactly would be the overheads in order to maintain different versions of MySQL from the application, operations and maintenance points of view.
As a DBA I see no problems to go directly to 5.1.31 if we upgrade anyway this client.
Containers like Docker and Rocket are getting more popular every day. In my conversations with customers, they consistently ask what containers are and how they can use them in their environment. If you’re as curious as most people, read on. . .
Learn several ways to interact with files and get file information from the bash shell.
ls lists the contents of a directory: Using the -a flag displays hidden files: Using the -l flag formats the output in a long list: The file command gives us mor…
Learn how to navigate the file tree with the shell.
Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…