I am bit novice in some aspects here and no related information found...
I have an AWS instance with mysql client installed at 5.5 version. And also an RDS db instance with mysql 5.6 (in order to use t2.micro). I don't think so but, could this in your opinion/experience produce some kind of trouble when requesting queries (via PHP, specifically Symfony2) between them?
I hope it is no; but if yes, is strictly necessary then to upgrade my mysql client in the instance or there is any other way to use t2.micro with mysql server at 5.5?
Any guidance or related experience would be much appreciated.
See Upgrading from MySQL 5.5 to 5.6:
Note particularly any changes that are marked Known issue or
Incompatible change.
That said, your client app should be able to use 5.6 safely, and you got it right, that is required to use db.t2.micro instances.
Related
This section of the MySQL documentation (https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-api-changes.html) states that API changes will be required when moving from 5.1.x to 8.0, however, can a db connection and with simple operations still work if attempting to use com.mysql.cj.jdbc.Driver with 5.1.x connector?
Judging from https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-versions.html, the connector is not compatible with MySQL server version 5.1. The stated compatible server versions are 5.6, 5.7 and 8.0.
However, I wouldn't be discouraged myself to give it a try. If you have good reason to upgrade your app code, but keep your server version back, it might very well be worth a shot. Client/server protocols don't tend to change that much. Of course, this would involve testing your application code, but you would need to anyway.
That being said, obviously, upgrading your server is the better and more future-proof route.
I was trying to use the AWS RDS Proxy service and realized that the only compatible versions with the service are AWS Aurora.
The current database I have is a MySQL database using MySQL version 8.0.20. AWS Aurora is MySQL compatible but only with version 5.6 and 5.7. I am not overly familiar with these versions and how different it would be to version 8.0.20.
Has anyone gone through the process of converting a MySQL database to Aurora? I know there are docs on the subject out there but they deal with version 5.6 or 5.7, has anyone done it for later versions?
I have all the MySQL code in SQL files along with the stored procedures so the database creation can be automated to an extent, it would just be if anyone has ran into issues doing it/found a better way than running multiple SQL files to transfer over data.
If you have gone through the process are there major differences between MySQL and Aurora in terms of running stored procedures etc?
MySQL 8 is now supported in AWS Aurora: https://aws.amazon.com/blogs/database/amazon-aurora-mysql-3-with-mysql-8-0-compatibility-is-now-generally-available/
They include the migration path in particular through a read replica promotion or full snapshot restore from rds into aurora.
Aurora 3.01.00 is the first public GA version of Aurora MySQL 8 released 2021-11-18 -- https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.3010.html
I've written a full tutorial of the upgrade process including the multiple options for pre-checks to ensure maximum compatibility at https://github.com/ronaldbradford/aws-tutorial/blob/main/rds/mysql-aurora-major-upgrade.md
I've scoured the MySql website to see if they have compatibility listings for MySQL Workbench, but have not found anything. Does anyone know if 6.0.x can connect to 5.5.x databases? I'd rather not install and then have to roll back.
MySQL Workbench can connect to most MySQL server versions, but that is probably not the primary question. You should rather ask what minimum version it can work with. MySQL Workbench requires at least MySQL 5.0 and can work with any MySQL server after that (including the new 5.7). Some features like authentication plugin or performance schema support require higher server versions, though.
I am totally new to databases. I would like to create a database; I am going to make a small project which is going to use DB. I am going to use Maria DB as it is totally free for commercial use.
The question is: Can I use MySQL workbench program to create a database and then transform/change it to MariaDB?
From my experience -- Sure, you can use MySQL Workbench with MariaDB.
However, I have tried basic functionalities only, like queries, schema design etc. Not sure about compatibility of advanced features.
So my experiences are, yes you can use MySQL Workbench for MariaDB database designs.
However I needed to change the "Default Target MySQL Version" to 5.7.
This can be done by going to: Edit->Preferences in the menu. And finally to Modeling->MySQL.
Since the latest MySQL version, v8.x, the SQL statements are not compatible with MariaDB statements (like creating an index). MariabDB creating an index on a table:
INDEX `fk_rsg_sub_level_rsg_top_level1_idx` (`rgs_top_level_id` ASC)
vs
MySQL:
INDEX `fk_rsg_sub_level_rsg_top_level1_idx` (`rgs_top_level_id` ASC) VISIBLE
MariaDB can't handle this VISIBLE keyword in this example. Using an old MySQL Version, MySQL Workbench will forward engineer a compatible MariaDB SQL file.
Currently (Oct 2019) the generated SQL_MODE output is still compatible with MariaDB. Just like InnoDB, which is also preferred when using MariaDB in most cases.
Just to list a few other options:
MySQL Workbench
Heidi Sql
SQLyog
No.
The latest version of Workbench 8.0 is not supported in MySQL.
Yes, although connecting to view existing database on a remote MariaDB server will crash the current client (6.3.10). I use it mainly to deploy database models and that works fine, even on remote servers.
I just deployed to a MariaDB 10.3 server with that client and it worked fine, see screenshot.
We have just begun to think about a new project where it will be crucial to handle fractions of seconds. We will use apache as web server with php.
We will get date data like: 2012-03-31 18:20:10.015493 and want to store it in db.
After some research i noticed that mysql didn't support the fractions before version 5.6 or something. This version seems to be in development stage and therefore I don't want to use it.
What is your recommendation, use another database server or store the date as another data type in mysql ? The demands on another db server is that its compatible with apache and is open source, running on unix.
Anyone got any tips or pointers?
In PostgreSQL:
SELECT CURRENT_TIMESTAMP;
Result: 2001-12-23 14:39:53.662522-05
See more here
You should also consider MariaDB (a mysql compatible fork). They support microseconds in the current stable version (5.3).