IT Central Station is now PeerSpot: Here's why

MySQL OverviewUNIXBusinessApplication

MySQL is #1 ranked solution in top Open Source Databases and #3 ranked solution in top Relational Databases. PeerSpot users give MySQL an average rating of 8.0 out of 10. MySQL is most commonly compared to Firebird SQL: MySQL vs Firebird SQL. MySQL is popular among the large enterprise segment, accounting for 63% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a comms service provider, accounting for 30% of all views.
MySQL Buyer's Guide

Download the MySQL Buyer's Guide including reviews and more. Updated: July 2022

What is MySQL?

Until its recent acquisition by Oracle, MySQL was possibly the most renowned open source database enterprise package that could be accessed completely for free. With the merger, the server increased both its features and its price tag, but there is still a free version available to the general community to contribute ideas and suggestions.

MySQL is a fast and relatively inexpensive database management system. It can easily integrate with a wide variety of programming languages, and it is considered to be a very reliable option. One of the most prominent features that customers seem to enjoy is the easy scalability of this system.

MySQL Customers

Facebook, Tumblr, Scholastic, MTV Networks, Wikipedia, Verizon Wireless, Sage Group, Glassfish Open Message Queue, and RightNow Technologies.

MySQL Video

MySQL Pricing Advice

What users are saying about MySQL pricing:
  • "Microsoft licensing for SQL Server is probably ten times more expensive. I used to work for the government, and I remember when we were looking into upgrading to the enterprise version of SQL Server 2019, the licensing was going to cost 350,000. To get the equivalent in the cloud, it was going to be about four grand to get the same processing power and everything else. With MySQL, it was going to be about 300 for the same licensing. Cost-wise, for sure, there is a huge difference. Would you prefer to pay 300 a month or 3,000 to have the same amount of data resources? You might lose a few options that you need, but it isn't worth the price difference."
  • "We are using the licensed version of MySQL."
  • "It's an open-source database management system that can be used free of charge."
  • MySQL Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    Arief Gunawan - PeerSpot reviewer
    Product manager at Metrodata Electronics Tbk PT
    Real User
    Top 5
    Has a simple and user-friendly installation
    Pros and Cons
    • "The one interesting thing about this product is that it is open source. It comes from an open source product. MySQL has been positioned as open source, but it also provides support."
    • "If the customer is already using or has already used Oracle for a long time they will know the look and feel and the character of this database that can fit into their business."

    What is our primary use case?

    We sell MySQL to customers who need to build second tier applications, not their core application. For some of our customers, when they are planning to build their second tier application, they will choose MySQL rather than Oracle which is more expensive.

    What is most valuable?

    The one interesting thing about this product is that it is open source. It comes from an open source product. MySQL has been positioned as open source, but it also provides support. Therefore, for a senior level product like MySQL it is different than a product like MariaDB or MongoDB which are also open source databases but they depend on the community for support. 

    People just assume it is less expensive. The product is not expensive. But they also have a strong principle behind data backup and supporting that product. That's why it's quite interesting, because it's open source but it has a principle behind it.

    What needs improvement?

    In terms of what could be improved, some of the features that Oracle has, MySQL also has. Like if a customer is looking for a high availability solution, a security solution, a monetary solution, they can have all that in an expensive product like Oracle but they can also have it when they're using MySQL.

    Every product has their own pros and cons, and also has their own market. So if the customer is already using or has already used Oracle for a long time they will know the look and feel and the character of this database that can fit into their business.

    They will not choose MySQL over Oracle if they already know about Oracle. But if they start to build a new application before they are creating a secondary application then they may not be familiar with Oracle and they will try MySQL. Maybe they will like it because they will see that this database also has complete features. If they try Oracle they find the same features but different pricing. In certain things, MySQL cannot have the same benefits as Oracle but for some customers who are already using Oracle, you're not going to move to another product even if it's more expensive.

    And MySQL is a cheaper product.

    That's why I say that MySQL has many of the same features as Oracle. Both of them have high security.

    The customer that comes from a small or medium business will prefer to choose MySQL rather than the Oracle database because they already know that this product is best for their business because it is not expensive compared to Oracle. 

    Oracle does have different versions with different prices. The cheaper is called the Standard Edition. And the most expensive is the Enterprise Edition.

    MySQL is comparable to the Oracle Standard Edition if we compare peer to peer. But the difference is that the Standard Edition doesn't have features like the Enterprise edition. But the high security and the high probability are not in the Standard Edition. But MySQL will have it. It will have all those kinds of features with a lower price. Because the Standard Edition is more expensive than MySQL.

    Every kind of enterprise company has a core application on which their business depends. Mostly they will just choose the Oracle database. Why? Because of Oracle database's capability to handle the big workload for enterprise businesses. I think that will become their priority and MySQL will not be an option for them.

    But someday I would like to see the enterprise companies changing their mindset. If you are talking about core applications related to the high workload in the future, they can choose MySQL as well. Maybe not now, because right now they still see MySQL as for small/medium business and not for the enterprise business. But I hope in the future MySQL can be seen as on the same level for their database.

    That will mean that all enterprise companies can have two options when they are choosing a database solution for their core application; either Oracle database or MySQL.

    For how long have I used the solution?

    I'm a reseller of MySQL. I've been selling this product for one or two years.

    Buyer's Guide
    MySQL
    July 2022
    Learn what your peers think about MySQL. Get advice and tips from experienced pros sharing their opinions. Updated: July 2022.
    620,987 professionals have used our research since 2012.

    What do I think about the stability of the solution?

    In terms of stability I think MySQL is categorized as a stable product. We have customers who are using MySQL as its database as an online application and it's like an online store. So it means that the work is quite heavy but we are using MySQL for it. 

    What do I think about the scalability of the solution?

    In terms of scalability, because the application is online, MySQL grows when their business grows and expands with the system. They may need to add more servers, but when they add more servers it means MySQL also expands.

    MySQL has that kind of capability - when the servers grow they have some kind of clustering method or clustering concept, which makes it scalable onto several servers. So it will follow the growth of the servers to cover the business.

    How are customer service and support?

    I have been handling Oracle products for more than 10 years so I know about their kind of technical support characteristics.

    For MySQL, when the customer has a problem they get their support from the Oracle portal. That means, the manual of support is online and the customer needs to register on the portal and if they have some issue or some problem using the product they need to create a ticket, and escalate or submit the ticket to the portal. Later on, they will get support from Oracle support which is worldwide.

    They have their own SLA for giving support because they apply a severity level depending on how you categorize the error.

    The highest severity is severity one. I think there are three or four levels. When the problem is not income to the business, you can categorize as a level three, it's a normal error. But if the error or the condition is impacting the business you can assume that is a severe one. So if you create a ticket and mark it as severe one then Oracle will directly contact Oracle support. They will contact you to help you to solve the problem within five minutes.

    How was the initial setup?

    The initial setup is categorized as a simple and user-friendly installation. It is not complex.

    I have experience installing Oracle, and if you just do the default install without too many customization, you can finish it in about one or two hours. For MySQL I think it is one hour to complete the installation.

    What's my experience with pricing, setup cost, and licensing?

    In terms of license cost, I think the one that we are selling for MySQL is not a perpetual license like we are selling for the Oracle database.

    The Oracle database license we are selling is on a perpetual basis. MySQL has that too, but for MySQL we are selling only the support.

    That means that the subscription we are selling for one year consists of software support for MySQL.

    That's the difference between Oracle and MySQL.

    What other advice do I have?

    My message to our customers out there is that you want to get a good product. A good product in terms of the cost and an effective solution. But you also need some guarantee that this product will be supported by the principle.

    Because there are so many cheaper products out there but they don't have principles to support the product. They rely on the community for the troubleshooting.

    So I recommend to the customers to try this product. MySQL comes from open-source so it means it's a cost-effective solution. But the important thing is this product has its own principle that is supporting this product. It means you don't have to worry as long as you have a bit of a principle behind you to cover and support you. So you can use this product with less worry because you have a principle behind you. That is my message to the customers.

    On a scale of one to ten, I would give MySQL an eight.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: My company has a business relationship with this vendor other than being a customer: Reseller
    PeerSpot user
    Database Engineer at a retailer with 10,001+ employees
    Real User
    Top 5
    A great open-source product that offers great scalability and compatibility
    Pros and Cons
    • "MySQL is open-source. There are a lot of open-source communities trying to come up with their own patches, and to come up with their own features, which help MySQL develop faster than traditional databases like Oracle, which is closed source."
    • "They should come up with a better solution than the NDB cluster for better scaling. If they could come up with a better solution for write scaling, apart from the NDB cluster, which is supported by all open source communities, that would be great. Although the NDB cluster, I believe, is an open-source tool, it's not widely supported as a solution."

    What is our primary use case?

    It's been used as a primary relational database for most applications. It's scalable and could easily be maintained and could be migrated to any Cloud-based Database as a Service solutions which are compatible with MySQL.e.g. AWS RDS MySQL, AWS RDS Aurora, Google SQL. 

    How has it helped my organization?

    It has improved scalability, easy-maintenance. It is open-source and is easy to use. 

    What is most valuable?

    MySQL is open-source. There are a lot of open-source communities trying to come up with their own patches, and to come up with their own features, which help MySQL develop faster than traditional databases like Oracle, which is closed source.

    The solution is also compatible with a lot of other databases, like Percona, and it's compatible with MariaDB. It's also compatible with a lot of other shared database solutions.

    Since MySQL is mostly used as a relational database in a lot of organizations, a lot of other solutions are being merged with MySQL and it's a rather easy process.

    Unlike a lot of closed source services, the new features are solely based on customer feedback. The customer feedback of open source is way larger than the closed source application.

    What needs improvement?

    The developers of MySQL, which are Oracle MySQL, Percona, and MariaDB, seem to not be focusing much on object-oriented replication. Basically, replication is based on a text level of replication. There is a text level replication in Oracle, that is so similar it can be implemented in MySQL, however, it needs to pull a lot of resources. They have altered their approach for replication. Still, more focus on object-oriented replication would be good. 

    They should come up with a better solution than the NDB cluster for better scaling. If they could come up with a better solution for write scaling, apart from the NDB cluster, which is supported by all open source communities, that would be great. Although the NDB cluster, is an open-source tool, it's not widely supported as a solution.

    The latest 8.0 version has come up with whole new features. 

    For how long have I used the solution?

    I've been working on Relational Database MySQL throughout my career, i.e. for 14 years. This relational database MySQL is evolved from its MyISAM only engine to InnoDB and is now compatible with other database engines too. e.g. NDB, Galera. 

    What do I think about the stability of the solution?

    MySQL is reliable. If you are talking about it in terms of relational databases, MySQL is pretty stable. If you want to go ahead with a quite secure database like any PCI database or a customer-related database or even financial data, it's still feasible to migrate to MySQL. 

    What do I think about the scalability of the solution?

    There are a lot of features provided by Oracle MySQL, Percona, and MariaDB. They all have their own replication cluster. Percona has XtraDB, MariaDB has GaleraDB, Oracle MySQL has its own cluster as well. MySQL replication is common in all three MySQL flavors. MySQL replication is an excellent read-scalable feature, which has also evolved a lot from its earliest versions to the latest 8.0 version.

    The NDB cluster, which has been supported and developed by Oracle, and is based on MySQL, is different than all of the other MySQL replication cluster solutions. It's both read and write scalable. All other cluster features work well for read scaling. NDB cluster is the only cluster feature recorded by Oracle MySQL, which is write scalable as well as re-scalable.

    How are customer service and support?

    The solution seems to have plenty of technical support due to the fact that there are three companies who are product owners, and therefore there are three companies who are supporting MySQL. They are: Oracle, Percona, and MariaDB. They're doing pretty well. 

    There are a lot of companies also that support their customers. This is the good thing about any software which is open-source. A lot of open source communities come up with their own features and they try to patch up with the original source. 

    How was the initial setup?

    The initial setup has evolved a lot. It's pretty straight forward whether you're using Mac, Windows, Linux, etc. You can set it up on almost every operating system. 

    It's supported by the open-source community, and they have plenty of documentation online that users can reference for assistance. If you are working in almost any operating system and you have any questions related to the installation, you'll find the documentation you need.

    What's my experience with pricing, setup cost, and licensing?

    I am not sure, what the licensing costs are for the solution. From my experience, there is no straightforward cost. You can get that cost from the Oracle website about the Oracle MySQL licensing costs, however, it's not a straightforward price quote for everyone.

    If you are an existing customer, you can negotiate and you can get a better quote. The pricing on the website may be for new customers. That said, you can still negotiate. The same is true for Percona and MariaDB as well. 

    What other advice do I have?

    We are using MySQL 5.6, 5.7, and MySQL 8.0. 

    In terms of advice, I'd say when implementing MySQL, if a company has been using any previous relational database, like Oracle, Microsoft SQL or DB2, the easiest way to migrate from any database is from Oracle to MySQL. There'll be some challenges from Microsoft SQL, as well as from DB2 to MySQL. Any existing application which is working with the Oracle database as a backend database, DB2 database as a backend database, or Microsoft as the backend database, should still work fine with MySQL, with minimal code changes. 

    MySQL is a product supported by a lot of applications and a lot of organizations. Almost every client and every API would be able to support MySQL. There would still need to be a lot of testing, however, I feel almost all of the applications which need a relational database for their database solution, could leverage out of MySQL. 

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Buyer's Guide
    MySQL
    July 2022
    Learn what your peers think about MySQL. Get advice and tips from experienced pros sharing their opinions. Updated: July 2022.
    620,987 professionals have used our research since 2012.
    Computer & Information Systems Manager at a real estate/law firm with 51-200 employees
    Real User
    Provides a simplistic view for building custom queries and has less performance overhead
    Pros and Cons
    • "I like the simplistic view of MySQL to build custom queries and things like that as compared to SQL Server, which seems more cluttered. SQL Server has a query analyzer. MySQL pretty much does the same, and performance-wise, it has less overhead for connecting to our ERP system. It seems more responsive and cleaner. With MySQL, you get what you need without any overbloating, for which Microsoft is known. That's why they have so many constant security patches for everything because there is so much stuff, which degrades performance."
    • "The GUI interface probably can be improved. Let us say I want to see the relationships in the database. In the query analyzer, I would like to go and drop the tables and create relationships between the tables. I haven't found a feature like that in MySQL. It was a shortcoming even in SQL Server. MySQL can have more performance monitoring tools. I know Google has these tools, but within MySQL, there are not that many tools to monitor things like performance and database locking. They might be in there, and I might not be familiar enough to know where they are. I am a pretty new user of MySQL."

    What is most valuable?

    I like the simplistic view of MySQL to build custom queries and things like that as compared to SQL Server, which seems more cluttered.

    SQL Server has a query analyzer. MySQL pretty much does the same, and performance-wise, it has less overhead for connecting to our ERP system. It seems more responsive and cleaner. With MySQL, you get what you need without any overbloating, for which Microsoft is known. That's why they have so many constant security patches for everything because there is so much stuff, which degrades performance.

    What needs improvement?

    The GUI interface probably can be improved. Let us say I want to see the relationships in the database. In the query analyzer, I would like to go and drop the tables and create relationships between the tables. I haven't found a feature like that in MySQL. It was a shortcoming even in SQL Server.

    MySQL can have more performance monitoring tools. I know Google has these tools, but within MySQL, there are not that many tools to monitor things like performance and database locking. They might be in there, and I might not be familiar enough to know where they are. I am a pretty new user of MySQL.

    For how long have I used the solution?

    I have been using MySQL for three months.

    What do I think about the stability of the solution?

    It has very good stability. We haven't had any issues with it.

    What do I think about the scalability of the solution?

    It has good scalability. You can use the Google interface to build it on the cloud. If you start noticing performance issues or you see it taking up memory or resources, you can add another processor. It is pretty easy to do. Right now, we are in beta. We haven't rolled it out completely to the people.

    How are customer service and technical support?

    I haven't had to use their technical support. They have plenty of online resources. If you have any problem, you can just search for it and find the answer. Somewhere, someone has done it before.

    Which solution did I use previously and why did I switch?

    The ERP company that we work with is moving away from SQL to MySQL. From my understanding, it is because of the cost. MySQL is also more streamlined and gives them what they need. 

    Even though I am a SQL Server person, MySQL has come a long way from what it used to be. They have made great strides. It seems like Google is moving more and more to it. In Google Data Studio, which gives you an interface to build dashboards, when you try and connect to new resources, you will notice they prefer MySQL on the cloud or a private server. Google is leaning more towards the MySQL side of things, and they make it very easy. It is a lot more work trying to connect to SQL Server. MySQL seems to be the preferred cloud database that people are going for.

    How was the initial setup?

    The initial setup was straightforward. MYSQL installation has fewer options than a SQL Server installation, which has endless options. MySQL installation is more straightforward and streamlined. It doesn't have a lot of extra features. It is just a database. It is a database engine that gives you what you need, and I like it.

    I am doing one installation right now on Google Cloud. I am building an instance of MySQL. It is just more simplistic. It is more to the point and what you need. In SQL Server, you need to dive into the endless options, and you use maybe 60% of what is there. There is a lot of stuff that people don't use, which you end up uninstalling because it affects the server performance, and it is a service that you are not even using. There is a full install as well as a custom install with SQL Server. If you go for the full install, it throws everything into the server, and you start noticing performance issues. Then you realize that there are services that you are not even using. Some places don't even use analytics or reporting services.

    What's my experience with pricing, setup cost, and licensing?

    Microsoft licensing for SQL Server is probably ten times more expensive. I used to work for the government, and I remember when we were looking into upgrading to the enterprise version of SQL Server 2019, the licensing was going to cost 350,000. To get the equivalent in the cloud, it was going to be about four grand to get the same processing power and everything else. With MySQL, it was going to be about 300 for the same licensing. 

    Cost-wise, for sure, there is a huge difference. Would you prefer to pay 300 a month or 3,000 to have the same amount of data resources? You might lose a few options that you need, but it isn't worth the price difference.

    What other advice do I have?

    If you want just a database for data storage, I would recommend MySQL. If you want something that has everything in it, such as reporting services and analytics, SQL Server might be better. Cost-wise, MySQL is almost pricing itself out.

    I would rate MySQL an eight out of ten for ease of use, especially for someone who has never used it and implemented it. It was pretty straightforward to implement it. It gives you what you need. It surely provides the basics such as data storage, setting up the tables, etc.

    Which deployment model are you using for this solution?

    Private Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Software Engineer at a financial services firm with 10,001+ employees
    Real User
    Top 20
    High performance, simple to use, and straightforward development
    Pros and Cons
    • "MySQL is easy to use, has fast performance, and it is comfortable for end-user to use. The schema level and structure we are using are very simple and easy to understand. Additionally, packaging tool development is straightforward and the data is presented in a way that is very simple to understand."
    • "In an upcoming release, there should be something added similar to EPL. For example, when using the flow diagram, we can create a schema. We have two useful features to add or create the table, but there should be some UI features to allow us to drag and drop to create other schemas. This would be very helpful."

    What is our primary use case?

    We are using MySQL for backend operations since we are a software backend developer. We are using this tool in our backend application for acquiring the data.

    We mainly use MySQL for our Relational Database Management System(RDBMS). We are maintaining our customer data in a defined way. We have to create various schema levels. We are presenting the customer data, such as name, mobile number, what was purchased, and what they like or dislike. Once we create the schema, a set of data, we need to maintain the unique constraints.

    For example, for customers, we'll assign a unique ID to each record, that will be a primary key. All these SQL constraints we'll use and there should no variance or replication of data isolated. When we perform any update operations, it should not affect any of the data isolated. 

    We need to take care of many things, such as consistency, isolation, and variability for constructing any database. There are a few more concepts as well, such as normalization and PL/SQL. For example, if I want to run a job at a particular time, the product will use PL/SQL. We are like implementing our coding skills to databases.

    Our operations are on-premise. However, we are in the process of moving everything to the cloud.

    How has it helped my organization?

    We have many repositories in one table that we are completing for customers' data that are store product data. There are various pieces of data and data should be in the same format. For this purpose, we are using RDBMS. The data in the repository should be able to be accessed in one place which is Oracle SQL Developer. MySQL can store data for a longer duration as compared to other data solutions, such as MariaDB, which can only store data for one day. MySQL can store data for a longer period of time, and we can have primary and secondary data as well for backup purposes.

    What is most valuable?

    MySQL is easy to use, has fast performance, and it is comfortable for end-user to use. The schema level and structure we are using are very simple and easy to understand. Additionally, packaging tool development is straightforward and the data is presented in a way that is very simple to understand.

    What needs improvement?

    MySQL can improve some of its functions. However, it is dependent on the use case. For example, if we are having multiple database connections in this tool, and we are performing one operation in one database, it takes a lot of time due to the reason we are selecting and processing the data. When we have a lot of data it takes a longer time. The transaction gets stuck in a queue and if we try to stop that particular transaction, it won't abort until all the selected records have been processed. This sometimes can be a lot of time and it can hold up our live processing of transactions. This product should be able to handle multiple processing at a time.

    In an upcoming release, there should be something added similar to EPL. For example, when using the flow diagram, we can create a schema. We have two useful features to add or create the table, but there should be some UI features to allow us to drag and drop to create other schemas. This would be very helpful.

    For how long have I used the solution?

    I have been using MySQL for approximately four years.

    What do I think about the stability of the solution?

    I have found the development tools to be highly stable in MySQL.

    What do I think about the scalability of the solution?

    The scalability of MySQL is very good. There are no barriers to it. It can be used and accommodated in any particular language. We can use it with Java and Python.

    We have almost everyone in my organization using the solution. We have developers and support teams all using it. If my organization has 1,000 people, almost 900 people out of them were using the service.

    Which solution did I use previously and why did I switch?

    I have evaluated MariaDB.

    How was the initial setup?

    We use a solution called Jenkins to help us with all the pipelines. The pipelines are all created and configured in the Jenkins. We are in a distributed server architecture and the full process can take approximately 20 minutes for one server.

    What about the implementation team?

    If we have a large amount of data we have to take care of it. If this particular data is not used over the years, we have to make maintenance decisions on it after we use it. The developer administrator and the team will be responsible.

    What's my experience with pricing, setup cost, and licensing?

    We are using the licensed version of MySQL.

    What other advice do I have?

    I would advise others that this is a useful tool.

    I rate MySQL an eight out of ten.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Specialist Geosciences Data Consultant at a energy/utilities company with 10,001+ employees
    Real User
    Top 5
    Simple to use, good for data manipulation and creating views
    Pros and Cons
    • "It is pretty simple to use and I don't have anything really bad to say about it."
    • "I would like to have the ability to cancel a query in SQL Developer."

    What is our primary use case?

    My daily tasks are related to data mining and TBICO Spotfire is one of the products that I use. We are a small group of geologists operating in a niche area who are analyzing geochemical data. Our backend database is MySQL and we use products such as Power BI, Tableau, and Spotfire to display data for the geochemists.

    I perform data-related tasks such as data manipulation and creating views, then updating the database afterward, all using SQL queries. As part of this, I'm making entries as needed or corrections to data that has already been processed.

    How has it helped my organization?

    Essentially, I'm doing data mining with SQL queries, although I wouldn't call what I am doing Data Mining exactly, because I already know the data model. I know the geochemistry data in my head, so I already know what I'm looking for when I write an SQL query. We're not doing machine learning or AI at this point, although it may come in the future.

    Every now and then, we create dashboards for the geochemists, which cover their needs from the data.

    What is most valuable?

    The most valuable component for me is SQL Developer. It is pretty simple to use and I don't have anything really bad to say about it. It supports multiple window displays and all of the connections are available. A lot of people use Toad for this type of work, but I have not myself.

    The functionality that I use most often is querying the data model.

    What needs improvement?

    I would like to see an autocorrect option, where if you're typing a query and you enter a comma instead of space, or something similar, the ability for it to be able to understand based on your previous scripts would be an advantage. For example, if you were to put a comma between your AND statements then it's not going to work. Maybe a smarter application where, as you're writing queries, similar to the way that grammar and spelling are checked when you type a text message on an iPhone, it could be autocorrected.

    I would like to have the ability to cancel a query in SQL Developer. Specifically, I would like to be able to cancel the query should I accidentally write one that's going to loop, or have a JOIN wrong, where you get millions of records joining with millions of records over and over again. The availability to hit cancel so that it doesn't keep running would be helpful because, when such a thing happens, then you have to shut down the whole application and you lose any queries that you might've typed before.

    For how long have I used the solution?

    I have been working with MySQL for approximately nine years.

    What do I think about the scalability of the solution?

    This application is pretty easy to scale.

    Within my department, which is technical data management, approximately 75% of the people use MySQL.

    How are customer service and technical support?

    I have never had to deal with technical support from Oracle directly. We just raise tickets that go up and show operations, and in turn, they are the ones that deal with Oracle.

    Which solution did I use previously and why did I switch?

    I have used several versions of Oracle MySQL including 10, 11, and 12, and I don't really see any difference between them.

    How was the initial setup?

    MySQL comes pre-installed with our new PCs, so I have never been involved with the initial setup.

    What about the implementation team?

    On the operations side, based on what I have seen in terms of people putting in tickets for issues, it seems that we have three people who support and maintain MySQL at different levels. I feel that having this number of resources assigned to maintaining a database is wasteful.

    I think that a single person can be in charge of maintaining multiple databases.

    Which other solutions did I evaluate?

    As a data analyst, I am not in operations and don't have a say in which products we use.

    What other advice do I have?

    My advice for anybody who is implementing MySQL is to ask around because there are many different ways that you can create a database now. Relational databases are no longer the best way to organize your data. It really depends on what it is that you're doing. For example, you may not need a relational database, but instead just a file structure. So, look at all of your options and speak with the experts to see what kind of database is needed before assuming that you need an RDBMS.

    I would rate this solution an eight out of ten.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Unemployed (previous role was Solutions Specialist, System Integration)
    Real User
    Has different licensing options and is easy to set up
    Pros and Cons
    • "The initial setup for the SQL database is not complex and it even integrates into the platform. You set up the recipe and then just follow the runbook, the build book. Then it works as long as you follow the procedures."
    • "Sometimes, not because the version is not the latest version, there are some issues with it. Sometimes there's an issue with the server which creates issues with it."

    What is our primary use case?

    I use MySQL as middleware to get the extracted data from the database. I work with MySQL as an administrator to set up the whole platform. And I document the recipe for setting up the MySQL database.

    We are working with the latest version.

    What is most valuable?

    SQL is just a relational database. It is open source. It's pretty good. I have been using it for a long time.

    What needs improvement?

    Because I am the middleware guy I'm not the SQL database administrator. If I have any issue with it, I'm going to contact the right person. Sometimes, not because the version is not the latest version, there are some issues with it. Sometimes there's an issue with the server which creates issues with it. Then, when the administrator checks the status and makes notes, it works normally and the problem is fixed. With a big company you are not going to work directly with the MySQL database. We are the end user and not the administrator of the SQL database.

    For MySQL, in terms of the usage or as the end user, I don't have much to recommend, as long as the query latency meets your requirements, it will be great. Otherwise, it's the horizontal scalability and you get more parallel in the implementation in terms of the SQL database regardless of the usage. This is probably much better than the vertical in terms of scalability.

    For how long have I used the solution?

    I have been using MySQL this year.

    What do I think about the scalability of the solution?

    If you are working in the cloud platform then you do have scalability because the cloud platform is usually AWS or GCP, and they provide this kind of scalability. If you get some issues with the query and latency or something like this, that is an issue of scalability and you can just adjust the horizontal or vertical scalability to meet your requirements.

    But the company I was working with was a very big company. It's more than several thousand people and they usually have a lot of data that they are going to store in the MySQL database. They gather the data from the SQL database and then transfer it like ETL and you get data from all the different distributed systems and then put them into the centralized MySQL database. After that you're going to visualize this kind of data so that you can use the Power BI or that kind of tool to generate reports or to create a dashboard for the system. This company had its platform on-premises, but right now they are moving these technologies to cloud. That's why I'm talking about the scalability in two different ways cloud and on-prem.

    How are customer service and support?

    For technical support, I'm the end user so I extract data or visualize the data from the SQL database. I didn't get too into the daily maintenance of the database.

    How was the initial setup?

    The initial setup for the SQL database is not complex and it even integrates into the platform. You set up the recipe and then just follow the build book. Then it works as long as you follow the procedures.

    What's my experience with pricing, setup cost, and licensing?

    Regarding the price, because it's the open source they have different licenses. Even for open source there's a license for the enterprise. I don't think it is expensive. Also for the scalability in the cloud, the price is based on the usage, such as, how much data you transfer.

    What other advice do I have?

    For the best usage right now, the trend is to move the platform from on-premise to cloud. Then, you you really have the best flexibility to scale down or scale up based on your usage. You can make full use of the resources and then pay for whatever you use. Because if you have it on-premise you always pay the same price no matter how much usage you have. So one of my suggestions is if you plan to set up the platform for MySQL, it would be best to go directly to the cloud solution.

    On a scale of one to ten, in terms of the usage for the middleware team and the end user of the SQL database, I would say it's around an eight at least. I cannot say from a  database administration perspective.

    To determine what would allow me to give it a 10, I would first have to get more experience using it on the cloud version.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    LeonMofor - PeerSpot reviewer
    Ingénieur Etude et Développement / Technical Lead Java at ATOS
    MSP
    Top 20
    Open-source, easy to install, and has good documentation, but scaling it can be difficult
    Pros and Cons
    • "The most valuable features are that it's free and the documentation is good."
    • "In the next release, I would like to see the scalability features improved to allow you to configure it and reduce the complexity with the configuration, making it easier for the end-user to scale. Make it as simple as it can be."

    What is our primary use case?

    MYSQL is our main database. We use it for every project.

    I use it for storage procedures, SQL administration, and database administration.

    We also use it for the development of reports, and projects that are deployed for our customers. It is also used to develop applications.

    The majority of companies use it for their development projects.

    How has it helped my organization?

    It's free. I'm in a big organization, with more than 100,000 employees. If you have to buy a database management system for every project, it would be very expensive. 

    Considering the cost-free option, you can use it for POCs,(proof of concept projects), and you can deploy it for customers to reduce project costs. The principal reason is that it is cheap.

    What is most valuable?


    Mysql is free : it's an open source project, so you can use it with no cost.

    Mysql is well documented, and has a big community.

    MySQL adheres to the current SQL standard, although with significant restrictions and a large number of extensions. Through the configuration setting sql-mode you can make the MySQL server behave for the most part compatibly with others like IBM DB/2 and Oracle.

    There are a number of convenient user interfaces for administering a MySQL server.

    MySQL has supported the storing and processing of two-dimensional geographical data. Thus MySQL is well suited for geographic information systems applications.

    MySQL supports the ODBC interface.


    For client programming you can use, among others, the languages C#, C, C++, Java, Perl, PHP and Python.



    What needs improvement?

    I would like to see a feature added to be able to handle high availability, which would allow us to scale the database or the system on many platforms.

    Scalability has to be improved, as you have only one instance of the application, or two, or more instances at max that are connected on one instance of MySQL.

    In the next release, I would like to see the scalability features improved to allow you to configure it and reduce the complexity with the configuration, making it easier for the end-user to scale. Make it as simple as it can be.

    Add the possibility to define custom data types 

    Add OLAP and backup capabilities

    For how long have I used the solution?

    I have been using MySQL for more than five years.

    What do I think about the stability of the solution?

    It is stable, and in fact, it's more stable than PostgreSQL. Also, recovery is faster.

    What do I think about the scalability of the solution?

    Scalability is difficult. You can scale it horizontally, but once you have many instances, it is difficult.

    You can improve the server, resources that are available, and the processor is good but if you want to scale it on many instances than it is a bit complex.

    We use it for customers. We have 10 instances of MySQL independently, on the project we are currently working with.

    How are customer service and technical support?

    It's an open-source solution. There is documentation available on the internet, that provides enough to resolve issues quickly.

    How was the initial setup?

    If you are a technician with practice, there is no issue, it's easy to handle. The documentation is available on the internet. You have everything you need quickly if you are autonomous.

    It's easy, you just download it, install it and click next until it's complete.

    What's my experience with pricing, setup cost, and licensing?

    It's an open-source database management system that can be used free of charge.

    What other advice do I have?

    I am not using the user interface because I'm a developer. Generally, I just try to find how to use the command-line interface to access what I want for the system.

    Oracle is still the best, but it's too expensive.

    Before purchasing this solution, know the needs of your environment and be sure that you don't have to scale it. If you want to scale it you will require more knowledge on the product and you will need more support for it.

    If you have a little project with a thousand users connected to the instances, it will be able to be scaled. But if you are looking to be able to handle large volumes this is not a good solution for your needs.

    If am comparing MySQL with other free solutions then I would rate this solution a seven out of ten.

    Which deployment model are you using for this solution?

    On-premises

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Google
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    goforitandy - PeerSpot reviewer
    IT Consultant at Woohoogeeks
    Real User
    ExpertModerator
    Free, cost-effective, with a powerful plethora of tools
    Pros and Cons
    • "Like other databases, it has a rich set of functions, such as stored procedures and its own procedural language, which is akin to Oracle SQL. It also has trigger and cursor commands you would expect with a good database language."
    • "MySQL tutorials and guides could be improved. Often they are too complex for someone with no database experience to understand."

    What is our primary use case?

    It is an ideal database to use online learning environments and SMEs. It works well with  Moodle, the open-source learning solution, and is the defacto standard for that product as Moodle is written in PHP which generally goes hand-in-hand with MySQL. As it is an open-source and free solution it is an economical method of storing important companies or small business data. At the same time, it offers a rich set of functions comparable to other large-scale enterprise solutions such as SQL Server and Oracle. 

    How has it helped my organization?

    MySQL is easy to configure, use, and implement. It is free, and cost-effective, with a powerful plethora of tools. It has improved my organization for my clients using Moodle and MySQL databases, as problems are usually easier to fix quickly, and the database resources can be optimized, easily. Even though it is not as sophisticated as SQL Server and Oracle solutions, it is the database of choice for most Moodle implementations. It has a history of reliability, which is always useful in a business environment.

    What is most valuable?

    The Cross-platform support for MySQL is great, as you don't need to worry about which platform or operating system you need to install the platform. This allows for interoperability.

    Like other databases, it has a rich set of functions, such as stored procedures and its own procedural language, which is akin to Oracle SQL. It also has trigger and cursor commands you would expect with a good database language.

    Views are updateable, which is useful when you need to amend a specific view of data for different circumstances.

    It has it's own Data Definition Language (DDL), and provides an Information Schema, to view what is "under the bonnet" of your database.

    What needs improvement?

    MySQL tutorials and guides could be improved. Often they are too complex for someone with no database experience to understand. 

    It is not an easy database to learn for the novice, and very often users need to take a course, employ the use of an online tutor, or IT professional to assist. Also, it is known that it is often difficult to locate guides for specific functions for developers.

    It might be good to have some way of creating web services easier, rather than having to write a User Defined Function (UDF) in PHP.

    For how long have I used the solution?

    I have been using MySQL for about 10 years.

    What do I think about the stability of the solution?

    MySQL has a reputation for stability, and that is one of the reasons it is so popular. Because it is easily available, just works, and can be integrated reasonably easily into other software, it is often the default platform of choice. 

    It has been around for years, and chances are it will be around for the next 10 years or so, as new versions continue to evolve.

    What do I think about the scalability of the solution?

    MySQL is scalable for SMEs and works on a number of different operating systems.

    How are customer service and technical support?

    I have not had many issues with MySQL in the past, so I rarely use the support service.

    Which solution did I use previously and why did I switch?

    I have used various databases in the past, but for my current business needs, MySQL is ideal.

    How was the initial setup?

    It was a simple setup, as it was included in the Moodle installation process for implementing learning sites.

    What was our ROI?

    ROI is not applicable, as MySQL is open source and is free, so you could say it is only the investment of implementing the database in your environment.

    What's my experience with pricing, setup cost, and licensing?

    Pricing depends on the size of your business. For an individual to SME sized business the MySQL solution should be adequate for your needs. Setup costs are minimal.

    Which other solutions did I evaluate?

    Yes, but for Moodle Learning sites, SQL Server is more complex, and is not multi-platform, Oracle is not recommended for Moodle, but the nearest to MySQL is ProstgreSQL. MySQL is reliable and easy to use. 

    What other advice do I have?

    You do need to have technical knowledge of databases in general, but MySQL is not too difficult to learn if used alongside PHPMyAdmin, but there are other tools you could consider, such as MySQL Workbench.

    Which deployment model are you using for this solution?

    Private Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Other
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user