MySQL Reviews

MySQL database is the database on which we run JD Edwards. You could run it on Unix or you could run it on Oracle or something else. Our choice was to run it on MySQL because of the availability of resources in our area. There are more MySQL database resources available around Houston than there would be those that are familiar with, say, Oracle Database.

The availability of resources for MySQL has been the biggest benefit for our organization.

I'd like to see Oracle provide more certification for it.

We've had no issues with deployment.

It's pretty rock solid and we've had no issues with instability.

We're able to scale without issues.

I cannot tell you when the last time was that I had to call about support for MySQL. It's really rock solid.

Choose your database based upon your ability to be able to hire people and support the product, like supporting JD Edwards with a MySQL database. Not everyone can work one database with JD Edwards as well as they can another one. So just make sure you've got the compatibility and skill-set.

I couldn't name just one most valuable feature. You can use it under different cases, but most of the time I needed the database as a part of my project. I think, in one moment you will prefer the InnoDB database, so you can store and execute procedures and roll-backs.

Again, I couldn't name an positive aspect precisely. Maybe, the fact that using MySQL and Java gives it a big portability and, at the same time, short time responses within your product (my case). This could come from the DB side. It also allows for easiness of finding interaction tools with MySQL.

None that I can name. At the moment I worked with MySQL, there was nothing I couldn't do with the product.

I've been using it for four to five years.

There were no issues with the deployment.

It's a pretty stable product for what I needed it to do.

There have been no issues scaling it.

Being a community product, you can find solutions all over the internet. It's not a specific support department.

There was no solution in use previously.

It was quite easy. The product comes with an installer. It can be complicated to configure the MySQL server, but with a little attention, all goes well.

It was done in-house.

It's free.

It helped me within my projects. For a free product, it works very well and it's easy to use and configure.

Don't try the most sophisticated products, that have big names, and cost a ton. Just try this product if you need something cheap and reliable. I don't think it will disappoint, at least not in my case.

• Privileges
• Command line

I don't have any as this was my first time using it.

I think it is where it needs to be. MySql PaaS. But, you do need to have experience with SQL to use it.

I've used it for 12 months.

There were no issues deploying it.

It has been perfectly stable for us.

We've been able to scale it without issue.

4/10

7/10

MS Access. It wasn't compatible with my project.

It was a straightforward set-up.

We used an in-house team.

We also looked at Microsoft SQL Server.

Experience with SQL is vital. It is simple to learn and use.

At this time, pricing and footprint.

This database enabled us to web present our content in a cost efficient way.

I am not up to date on this issue.

At the time pricing and footprint.

This was the IT consultant's task to solve.

No issues encountered.

Not really, as our DB was small. With time, we got version issues, as our DB engine was so old and not updated.

I've never used it.

I've never used it.

No previous solution was used.

I don't know as we had consultants.

Consultant team.

We installed it under another now-obsolete license form (free on Linux).

No, as it was required for a CMS we implemented.

• Excellent performance, mainly due to the format of its default table, MyISAM - low disk space, CPU, and memory
• Flexibility offering multiple variations such as Berkely DB , InnoDB, Heap and MyISAM
• Reliability. Although the system runs on Windows without flaws, it tends to perform better on Linux and other UNIX-like Systems.
• Availability
• Open-Source System, open storage database engine
• Used by many websites (e.g. LinkedIn, Facebook, Verizon, and PayPal)
• It's inexpensive when compared to other common databases like Microsoft SQL Server.
• As a developer myself, I enjoy using it at no cost as long as the associated projects are also open-source.

• Limited storage capacity
• Support for foreign keys
• Stored procedures
• The biggest disadvantage of MySQL is MyISAM system, which doesn't support well transactions (lack of efficiency)

Personally, I've been using it for over 10 years, and professionally for three to four years.

I had no problems deploying it.

With each release of MySQL Server was useful for any little problems that users detected, so I would say it's quite stable.

It was straightforward, thanks to the workbench that pulls together nearly every MySQL task, and puts them into one easy and friendly GUI.

Because MySQL is an open-source , the system is under GNU Licence. The system isn't always free, but it's more affordable. If you intend to sell your software as a proprietary product, you would need to purchase a commercial license, which is quite inexpensive when compared with a Microsoft SQL license.

From my perspective, MySQL is a product that allows you to be efficient, but the decision goes down to the situation and what you're looking to accomplish.

• Reliability
• Security
• Flexibility
• Functionality
• Availability - controllability anywhere and with different methods

MyISAM tables could be more reliable.

I've been using the Workbench Server for six years.

I have had no problems deploying it.

I have no stability problems.

I currently do not need to scale on my network.

I only have the free version, which does not have customer service.

I only have the free version, which does not have technical support.

We use Cisco ASA and Nagios devices alongside the MySQL server as our network infrastructure needs expanding and required more serious hardware solutions.

I believe it is hard to calculate for hardware.

I only use the free version.

We also looked at PostgreSQL.

As a rule, any device upon delivery is obsolete. Pick up the solution for your business, based on your specific needs.

MySQL 5.6 has a great many new features, including, but certainly not limited to, a number of performance improvements.

However, besides the widely talked-about features such as InnoDB, there's also support for full text search, optimizer, performance schema improvements and GTID.

In order to change the size of InnoDB transaction log files, you have to follow this procedure. Beware that if you don’t follow these instructions step-by-step, your server may not restart or rather it will start with InnoDB storage engine disabled and an error in the logs. So, here’s what you want to do:

1. change (or add) the following variable in my.cnf: innodb_log_file_size = ..
2. stop MySQL server
3. make sure you see a successful shutdown of InnoDB in the MySQL error log
4. move away old log files (at this point I have to double check where they are) by running the following command:
mv /var/lib/mysql/ib_logfile* /tmp/
5. start MySQL server – it should take a bit longer to start because it is going to be creating new transaction log files
6. When you’re positive that MySQL server has started successfully, you can remove the old log files:
rm /tmp/ib_logfile*