Everything says XAMPP has MariaDB now, but using the latest download link it only has MySQL. Am I missing something? For my needs I'd rather use MariaDB, but can make due with MySQL if need be, but it might create some minor headaches down the road. Is it simply because I'm on Windows?
From the MariaDB Wiki:
MariaDB is a community-developed, commercially supported fork of the
MySQL relational database management system (RDBMS), intended to
remain free and open-source software under the GNU General Public
License. Development is led by some of the original developers of
MySQL, who forked it due to concerns over its acquisition by Oracle
Corporation in 2009.[6]
XAMPP (currently version 7.4.3) ships with MariaDB (currently version 10.4.11)
The current version you're using should come up when logging via the cmd line or if you do a SELECT VERSION();
You can find a full list of differences between MariaDB and MySQL here
Related
Upgrading the database version needs intensive testing.
Is it better to upgrade to latest version of MySQL workbench?
If we are installing previous versions of MySQL database, Is there any certification matrix to know all the corresponding version of MySQL workbench or what minimum version it can work with?
Mysql-Workbench using libmysql.dll. You must update this dll from your mysql\lib folder. So a lot function working same as before.
Ultimately, I want to learn MariaDB. I’ve found that there are hundreds more resources for learning MySQL than for MariaDB. My assumption is that everything I learn from a MySQL book will also apply to MariaDB since it’s a drop-in replacement for MySQL.
From the MariaDB website:
For all practical purposes, MariaDB is a binary drop in replacement of the same MySQL version (for example MySQL 5.1 -> MariaDB 5.1, MariaDB 5.2 & MariaDB 5.3 are compatible. MySQL 5.5 will be compatible with MariaDB 5.5).
Will I be able to use MySQL books to prepare for learning MariaDB or will they be useless to me if what I really want to learn is MariaDB?
If you take care about the few differences and incompatibilities (very few, mariadb starts from the same codebase than MySQL), you should have no problem using a resources from one DB and applying them to the other DB.
Even more so if you are mostly focusing in SQL syntax.
You don't really need to care about the differences, unless you are a very advanced user. MariaDB can replace MySQL with every application I know. Some MySQL 5.6 optimizations are not in MariaDB, but much more MariaDB optimizations are not in MySQL.
the company i work for is considering for multiple reasons (some of them libked to the politics of open source and oracle) a switch from MySQL to Mariadb. Our development team has been using Zend Server (now it's 6th version) which always install mysql. Is it possible to switch from mySQl to Mariadb smoothly? are there any hurdles that we should be aware of ahead of time? The OS for every development computer is Ubuntu 13.04 at this point.
No, there should be no more issues than when upgrading to a new MySQL version.
See How can I upgrade from MySQL to MariaDB?
I would like to replace MySQL 5.1 on my Debian Lenny 32-bit server to Percona Server with XtraDB. The main reason is better performance of Percona.
It's production server with many services running. Many other software may depend on mysql-client and other mysql shared libraries.
Is it safe to replace MySQL?
By "safe" I mean: 1. remove mysql, 2. install percona 3. everything works as before
Will it break dependencies in third party software?
Will it require to change configuration of third party software (ie. socket path, server port, shared libraries path)?
Will it require to install trillion of additional packages?
I really don't want situation with broken libraries, missing or incompatible header files and so on
We are currently in the process of upgrading from MySQL 4.1 to Percona Server 5.5 at work and Percona is as they say on their site a complete drop-in replacement for MySQL, the binaries use the same names, it uses the same libraries, same config file placement, takes the same parameters and it has exactly the same SQL syntax. They should also be data file compatible on the same version (MySQL 5.1 to Percona 5.1, etc) but it's nothing I've personally verified.
You are able to do an apt-get install percona-server-server-5.1 after adding their repositiories and it will automatically replace MySQL because it marks it as a conflicting package. But you must take an SQL dump of your database first, of course.
We currently have replication set up from a MySQL 4.1 master to a couple of Percona 5.5 slaves and have had no problems inserting SQL dumps either.
... don't know.
In my experience, the only way is to make up a copy of your existing setup on an old machine and run some tests. Then swap over to the new DB and run same tests again.
I just swapped a set of applications from Tomcat 5 to Tomcat 6 and in theory, with one or two tweaks, all should have worked fine. First time I tried it OpenJava was installed and the garbage collection fouled things up. Second time around with Sun Java, some dodgy date handling fouled things up and had to be corrected, seems to run fine now.
I understand that Oracle will at some point add support for MySQL to its Enterprise Manager software. However I'd like to know perhaps from other Oracle to MySQL migrants what tools are available for monitoring the queries, activity and resource usage happening on a MySQL database instance.
Take a look at MySQL Enterprise Monitor
One option would be MySQL Workbench 5.2. It's still in Beta but development is moving rapidly. They are replacing the old MySQL administrator with this all in one tool.