MySQL Reviews

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.

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.

My primary use case for MySQL is with my products or websites for clients, and it helps me maintain relations with the best.

The relations in the database, the dynamic workflow, and the ability to connect with all columns. It's useful for e-commerce.

There is room for improvement in terms of the stability of the solution. 

I have been using MySQL for three years. 

I would rate the stability a seven out of ten. It does break down a little at times. 

I would rate the scalability a seven out of ten. 

The initial setup depends. For example, when working with e-commerce sites, it can be difficult to connect, and there may be failures. However, for other sites, it's easy.

Our organization is using MySQL by having it hosted through a hosting provider.

It is free. It is an open-source platform. 

Overall, I would rate MySQL a six out of ten. I recommend MySQL for small organizations and companies. For bigger organizations, one may need to consider other options.

You can also consider your project, budget, and organization while opting for MySQL. If it's a government or private project and what the product is. 

MySQL can handle multiple rules of a database within seconds and extract required information for the business case, especially with well-optimized queries.

There should be an arrangement for end-users to get trained to use the tool. End-users don't know many things which MySQL offers to its users. So, there is a need for the end-users to upgrade themselves. Also, the tool is already good the way it is currently owing to its features like multithreading which helps with the queries quickly. In short, if one goes for the complex part, if one uses it for a very specialized case, then that person needs to write a very complex query involving multiple tables, multiple joints, and multiple conditions based on whatever scenario one uses.

Improvement-wise, a graphical interface could be added for new users, eliminating the need to memorize the complex syntax.

I have used MySQL for five and a half years in my company, but I have used the tool for around ten years.

MySQL is a stable tool. Stability-wise, I rate the solution a nine out of ten.

MySQL is a scalable tool. Scalability-wise, I rate the solution a nine out of ten. My whole company directly or indirectly uses the tool since we are involved in analytics. My company is an enterprise-sized one.

The solution's technical support is good. I rate the technical support a nine out of ten.

Positive

Since everyone in the industry we are a part of uses MySQL servers, we have also used the same.

The solution's initial setup depends upon the use cases. If you're using it for a simple thing, it's a simple process. But, my problems and statements are quite complex, and I use them to get information, like how the customers perform based on cohort analysis. Also, my use cases are complex, so I have to write complex queries. Overall, the setup process depends upon the scenario.

The installation process is not difficult since it gets pre-installed in all the machines after it is done once. Since the installation process is neither very easy nor difficult, I can rate it somewhere around seven out of ten.

The IT Department handled the deployment process in my current company. Based on my experience deploying the solution in my previous company, its deployment was not difficult. Since everything was already deployed in my current company, we are using the tool as front-end users. When planning to start using the solution, we need to launch SQL server before using it. Also, based on whatever datasets are there, we need to get the permissions for those data sets, after which we are good to go.

MySQL requires maintenance, while the IT department handles the maintenance of SQL server. I am not involved in managing the upgrading part of the tool. Every year, MySQL keeps releasing new versions with new functionalities.

My suggestion to those planning to use the solution is to learn about it and utilize it for their specific scenarios. It is a powerful tool that can perform multiple analyses and reveal hidden insights within multi-million or billion-row datasets that may not be immediately visible to the human eye. The tool also offers many use cases for machine learning. I encourage users to plan and explore the tool to discover its full potential. I rate the overall product a nine out of ten.

I am using MySQL for business data queries.

The most valuable feature of MySQL is its reliability and performance.

The GUI could improve in MySQL.

I have been using MySQL for approximately 12 years.

I rate the stability of MySQL a ten out of ten.

We have approximately 100 people using this solution.

We plan to increase the usage of the solution in the future.

I rate the scalability of MySQL a ten out of ten.

I have not used support from the vendor.

The initial setup of MySQL was easy.

I would recommend this solution to others.

I rate MySQL a ten out of ten.

Our primary use case for MySQL is for our internally-built system. When our developers are doing the assistance, usually we provision them with the MySQL driver.

The way that MySQL has improved my organization is that it comes free and also works fine on the technical side.

The feature I found most valuable was the cluster setup.

The integration with other systems can be improved as can the integration between other databases. We have a workaround to integrate it with other systems but that can be improved.

In the next release, I would like to see better day-to-day support in case we face any issues.

I have been using MySQL since 2008.

I would rate the stability of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best. We have a team of three DBAs supporting and maintaining this product.

I would rate the scalability of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best. I believe MySQL very scalable.

I would rate the technical support an eight, on a scale from one to 10, with one being the worst and 10 being the best.

Positive

I would rate the initial setup process a nine, on a scale from one to 10, with one being the worst and 10 being the best. I would say that this process has been quite easy.

The deployment of this solution was done by an in-house team and it took around 30 minutes to one hour.

I would rate the pricing of this solution a two, on a scale from one to 10, with one being not expensive and 10 being very expensive.

I would recommend this solution to other people.

Overall, I would rate MySQL solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

I have worked on migration projects between Power BI on Microsoft and SAP modules, which involve exchanging databases from Power BI on Microsoft to SAP modules. 

Additionally, I have been involved in integration projects as a MySQL developer using Oracle SQL databases.

MySQL has facilitated the migration projects to SAP modules from Microsoft Power BI, easing database exchange. The integration is smoother and more efficient, which has been beneficial for handling various projects.

The ML modules in MySQL are advantageous since they make data handling easy and quick at MNQM. I have a lot of experience with QA test sections on MySQL, and it aids in connecting with third-party programs effortlessly due to its adaptation capabilities.

MySQL has some unique exchange problems when it comes to migration projects. The product could improve in terms of security, though not necessarily when compared to Azure. It can be improved in areas related to database exchange during migration projects.

I have five years of experience with MySQL.

MySQL is stable and continuously improves concerning databases. It is advantageous for projects in this area.

Scalability in MySQL involves unique troubleshooting for every project that differs according to database exchanges. You can solve scalability issues easily if you possess strong SQL skills.

Technical support from Oracle for MySQL is very good. They are really good at providing support.

Positive

I have experience with Oracle SQL and have not used Microsoft SQL. MySQL and PostgreSQL are the tools I currently work with.

The initial setup for MySQL took about one and a half hours, and only one person was required for the installation.

Cost-saving is not a significant concern, but focusing on project details is crucial. The project details provide exchangeable areas that can lead to cost savings.

The pricing for MySQL is slightly expensive, especially in unique projects for sectors like automotive and pharmaceuticals. Despite this, it is preferable for special projects due to its unique offerings.

I have experience with Oracle SQL and PostgreSQL.

I'd rate the solution eight out of ten.

I use the solution for personal use cases like software development, mostly database bug systems.

I used the tool to build our website. It is used as a database to store information.

SKIP LOCKED is a valuable feature. It prevents us from deleting things we put in the database. It's mostly for background jobs in the software development site in MySQL 8. It is a new feature. The solution easily integrates with other tools and systems in our IT environment.

The full-text search feature must be improved.

I have been using the solution for the past three weeks.

I rate the tool’s stability an eight out of ten. We can create a database user schema. It's quite easy to update and remove in case anything happens. Backing up is quite easy. We have security features for the backup.

I’m the only user in my organization.

The product provides good documentation online.

It is easy to deploy the product. I deployed it on my own. The deployment took an hour. We deploy the product using Kamal. It uses Docker. The tool is deployed on the cloud. To deploy the solution, we just have to enter the password in the server and deploy it. It wasn't much of a hassle.

The tool is easy to manage and saves us time. It has much less complications.

We're using the community version. The tool is open source.

I also use PostgreSQL.

The tool helps us get the job done. It is not very complex. Overall, I rate the product a nine out of ten.

We use the tool in projects with customer records in the database. There will be a front-end application to search and find specific data from the tool. In another project, there are product listings, and the front end fetches data from the tool and shows it in a gallery or list view on the web page or mobile application.

We used MySQL in a project for a nonprofit museum. They have a lot of donors. They have a large repository of customers who give donations. They categorize the customers based on the money they give, such as steward level, platinum level, and diamond level. The client may send out an invite for an event for a certain group of customers, such as the patrons who donate the most. MySQL helped us in that project.

The optimized process is valuable. I have seen websites that take ages to load and show the data. Many web applications with lakhs and lakhs of data will take forever to show specific results. The database performance is optimal for the application we developed. The speed is very good. There were no delays in fetching data from the back end and showing it on the front end.

At times, the autoscaling does not happen when there is a surge in load. We had to depend on manual scaling. It led to website crashes in the past.

We have been using the solution for projects running for the past five years.

Scalability is one area in which we are very cost-sensitive. We always closely monitor the charges to increase the server scale. It will help us use more space in the DB if there is an economical way for us to pick up larger servers. We have more than six lakh end users.

Most of our projects are on the cloud. A very small number are on the client's premises.

We are continuing to use the tool because it's been cost-effective. It's producing revenue for us. It's a beneficial solution.

The tool is open source. We choose open-source software mostly. We integrate a very limited number of licensed software.

I have not seen any incident with a security violation or data breach. I have not contacted the technical support team. The infrastructure team contacts the technical support team regarding server-related issues. There is a LAMP stack. The Linux, Apache, MySQL, and PHP combination seems to be working well for enterprises' modern web applications.

Overall, the integration works well. However, initially, we worked with a third-party integration team to fix the APIs, query, and response code. Initially, some technical work will be needed. Once it is done, the integration turns seamless.

Overall, I rate the product an eight out of ten.