I started to use MySQL at some point when I had some issues that I couldn't get around. I normally use the tool in professional opportunities and when I require support from MySQL.

Cacti is a tool for monitoring devices on a network in graphical terms, for which it uses MySQL or MariaDB. I mostly deploy Cacti with MySQL or MariaDB. Somewhere down the line, I started to have some issues with the permissions in MySQL, including its areas like superuser privileges and similar stuff, which took me a while to figure out. I think the tool is fine for me now.

The most valuable feature of the solution stems from the fact that it helps me to get my work done. I am more interested in getting my work done than any feature it comes with since, as long as it gets my work done, it can actually help me achieve my objectives.

Nowadays, I use phpMyAdmin or MySQL WorkBench to manage MySQL. I would have been in a position to comment on what requires improvement if I had spoken about the tool three years ago. There are no improvements needed in the UI of the solution since many tools in the market help the user get the job done. MySQL WorkBench belongs to Oracle.

The performance, stability, and security are areas with shortcomings in MySQL, where improvements are required.

It would be a great improvement if the product could be made affordable enough for me to be able to access support from MYSQL, especially when I deal with mission-critical applications.

I have been using MySQL since 2014.

It is a very stable solution. I deployed the product six years ago, and it still works fine.

I won't be able to comment on the product's scalability since I haven't deployed it in a cluster environment.

Our company has over a thousand devices, including switches and a couple of other devices, which report to MySQL for management purposes. In general, MySQL is a very robust tool.

Somewhere down the line, I got introduced to MariaDB as well. Nowadays, I use MariaDB rather than MySQL most of the time.

The product's initial setup phase is easy since I use package management software. I mostly take care of the deployment phase with the help of Docker and other tools. If you decide to use the default deployment settings provided by MySQL, then it is a straightforward process to deploy it.

A lot of things have changed since I have deployed the solution. The solution is like a new product nowadays since you just need an application to deploy it presently. The other area where you need to take care of the solution is knowing how to secure it very well so that it becomes less vulnerable and prevents people from taking advantage of the solution.

Mostly, I go to the MySQL website to download the binaries, and I just deploy them on a Windows machine or another system, which is just a straightforward process. The product's installation phase is not much of a problem.

The solution is deployed on an on-premises model.

Earlier in my company, there were three people who used to take care of the deployment of the solution, but presently, I don't know who handles the deployment part.

In the past, the product was free for users, which ensured that users could experience a high return on investment from the use of the solution. I don't know the licensing models attached to the solution currently, but the return on investment is very high if you use it for a very limited amount of time.

MySQL was one of the tools I was introduced to from the very beginning when I was in school. Though I knew about Microsoft SQL Server, the lectures in my school did not introduce me to it since more focus was placed on MySQL. I find MySQL easier to use compared to Microsoft SQL Server.

I recommend the solution to those who plan to use it since it is a very good product that comes to my mind since it is always available. I don't know about the current licensing model of the product because it was an open-source tool earlier. I don't remember myself attempting to check what kind of license MySQL uses presently. In the past, Microsoft SQL Server used to cost a lot of money, which my company couldn't afford at that time.

I rate the overall system an eight out of ten.

I've used MySQL in the past for a variety of tasks. 

I once used MySQL when I created a PostgreSQL database for club management tasks. This included handling registrations, events, and mailing notifications for payments and event details. It served as a source service provider.

The response time for support could be faster. 

MySQL's performance requires attention. For optimal performance, one should review and sometimes revise the code, particularly when using server-side scripting. To optimize performance, it's crucial to pay attention to your code. Sometimes, you may need to review your code to ensure it's efficient and doesn't unnecessarily access the database multiple times.

The performance issues I encountered were not due to MySQL itself but were related to my coding approach.

I have been using MySQL for ten years. 

I would rate the stability a ten out of ten. 

For my use case, it is okay. Basically, it's just me for development. Previously, all clients or members of the club accessed it. When there was an event, maybe 30 to 40 people would try to access the system simultaneously.

I'm using SiteGround for hosting the website and its servers. I've chosen a package with more than enough CPU and memory to avoid trouble.

I've used technical support for several times. Most of the time, it was quite okay with quick responses. Once, I had performance issues. It took some time to convince them, but they guided me on improving performance by changing some database functions in MySQL. It was a longer process, but it was eventually resolved.

Positive

The initial setup was easy. I work in an agile way, which means coding and deploying quickly. We had a few internal users but many external users accessing the website, though not the back office.

The back office was developed over years. It's not just about having an idea and executing it; it's more about testing and adapting the process, unlike the waterfall method, where you end up with something that may not be immediately usable.

As the main user, our deployment process wasn't as strict as in a big company. I conducted tests, had a testing process with use cases to review, and then deployed. It was less rigid than in larger companies, where there are separate testing and development environments.

I  have seen value and impact from using MySQL

I don't pay for a license. 

With my previous employer, we used Oracle.

Don't just use MySQL on its own. Always use it with other software around it. MySQL is very stable, but pay attention to the software you use with it, whether you develop everything from scratch or use open-source systems like CMS.

Overall, I would rate the solution a nine out of ten. I would recommend using the solution. 

I use the product as a backend to my application.

The product is flexible and easy to use.

The interface could be improved.

I have been using the solution for seven to ten years. I am using the latest version of the solution.

I rate the tool’s stability a nine out of ten. The stability is good.

I rate the tool’s scalability a seven out of ten. We have four direct users and more than 1000 indirect users. We use the tool twice a week.

I rate the ease of setup an eight out of ten. The deployment took a few minutes. We need two system administrators to maintain the tool.

The deployment was done in-house. We need one system administrator to deploy the tool.

I rate the pricing a seven or six out of ten on a scale of one to ten, where one is cheap and ten is expensive.

We used different solutions before, but I do not know why we switched to MySQL. I recommend the solution to others. Overall, I rate the product an eight out of ten.

We use it for building web applications and managing data.

It is quite efficient and performs well, especially when compared to MSCS. While traditional scaling methods can occasionally lead to slowdowns, I haven't encountered similar performance issues with MySQL scaling.

The installation process for the most scalable solution is remarkably quick, taking only a short amount of time. While restoration may theoretically take longer, I've achieved rapid setup with my system, often within a minute.

While utilizing a comparable algorithm, is noted to be sensitive, especially when configuring the inner device. If DCDR is not properly recovered from NDC, it can lead to system slowdowns. There is a need for enhancements in the InnoDB cluster, specifically the capability to support more than two nodes in MySQL. Additionally, the inclusion of data nodes would be a valuable improvement. For users new to the system, it might pose a bit of a learning curve.

I have been working with it for one year.

I would rate its stability capabilities eight out of ten.

I would rate the scalability eight out of ten.

When facing support issues with your server, the level of assistance is generally high. However, in certain technical support instances, when issues are raised and a ticket is generated, the support team sometimes provides a link for further information. From a customer perspective, this approach is not ideal, especially when dealing with critical problems such as database downtimes. The expectation is for more direct and personalized support rather than reliance on knowledge-base resources in urgent situations.

Positive

I utilize Microsoft SQL Server (MSSQL) and MySQL for most of my databases. However, there are certain limitations in the new versions that impact support for certain functionalities. Due to these limitations, I have turned to MySQL as an alternative.

The initial setup was straightforward. I would rate it eight out of ten.

The deployment process, which took an hour, involves understanding various versions, especially the enterprise version, and confirming compatibility with the required features. Installation includes accessing the Oracle site, downloading MySQL, and dealing with complex considerations due to multiple business packages. Challenges may arise during the download of the DVD packet, requiring a careful assessment of the business needs for MySQL installation. The subsequent steps involve uploading MySQL VPN, reinstalling, and following a step-by-step approach, taking about five minutes. Despite the relatively swift deployment, managing dependencies and collecting necessary packets can be time-consuming and pose challenges for users. Maintenance requires only one person, especially if that person has knowledge of system administration. However, incorporating a software manager or other managing tools can be beneficial. Configuring and monitoring these tools doesn't necessarily require constant attention solely from the individual responsible for maintenance.

It is an open source platform. While the free version of MySQL offers comprehensive features, it does come with limitations.

Overall, I would rate it nine out of ten.