MySQL is a popular open-source relational and embedded database, now owned by Oracle.
N/A
Toad Data Point
Score 8.0 out of 10
N/A
Toad Data Point is a cross-platform, self-service, data-integration tool that simplifies data access, preparation and provisioning. It provides data connectivity and desktop data integration, and with the Workbook interface for business users, it provides simple-to-use visual query building and workflow automation.
$365
Pricing
MySQL
Toad Data Point
Editions & Modules
No answers on this topic
Base Edition
$365
Pro Edition
$528
Offerings
Pricing Offerings
MySQL
Toad Data Point
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
MySQL
Toad Data Point
Considered Both Products
MySQL
No answer on this topic
Toad Data Point
Verified User
Analyst
Chose Toad Data Point
I have not used another tool that allows for these seamless connections so it is unfair to rate Tableau and Hyperion against this becuase they have different uses. But if I had to compare, Tableau does not make it as easy to connect to multiple datasources and definitely has …
MySQL is best suited for applications on platform like high-traffic content-driven websites, small-scale web apps, data warehouses which regards light analytical workloads. However its less suited for areas like enterprise data warehouse, OLAP cubes, large-scale reporting, applications requiring flexible or semi-structured data like event logging systems, product configurations, dynamic forms.
Appropriate for general querying and some DBA work. It's the universal least-offensive solution for most environments - not best of breed, but not subject to unusual/extensive requirements. It just works. On the other hand, some functionality (e.g. data import/export, snippets) are perfunctory and minimal and seem to be either difficult or impossible to automate. If you need to streamline those operations, you'll be forced to rely on third-party solutions that mostly work on top of (instead of with) TOAD.
Learning curve: is big. Newbies will face problems in understanding the platform initially. However, with plenty of online resources, one can easily find solutions to problems and learn on the go.
Backup and restore: MySQL is not very seamless. Although the data is never ruptured or missed, the process involved is not very much user-friendly. Maybe, a new command-line interface for only the backup-restore functionality shall be set up again to make this very important step much easier to perform and maintain.
The workflow is a relatively new feature. Quest is adding additional functionality and the workflows are useful now.
Would be nice if the 'Automate' feature was a bit easier to use.
Would be nice if some of the SQL Editor features in the traditional interface worked better in the new workflow interface (although, these are being fixed with each release).
For teaching Databases and SQL, I would definitely continue to use MySQL. It provides a good, solid foundation to learn about databases. Also to learn about the SQL language and how it works with the creation, insertion, deletion, updating, and manipulation of data, tables, and databases. This SQL language is a foundation and can be used to learn many other database related concepts.
I give MySQL a 9/10 overall because I really like it but I feel like there are a lot of tech people who would hate it if I gave it a 10/10. I've never had any problems with it or reached any of its limitations but I know a few people who have so I can't give it a 10/10 based on those complaints.
I find Toad Data Point easy to use for both the novice and the experienced business analyst. If all you desire is to access data and create spreadsheets...this is a snap. Toad Data Point actually has cool data analysis features built into it. The newer workflow interface makes automating steps a snap
We have never contacted MySQL enterprise support team for any issues related to MySQL. This is because we have been using primarily the MySQL Server community edition and have been using the MySQL support forums for any questions and practical guidance that we needed before and during the technical implementations. Overall, the support community has been very helpful and allowed us to make the most out of the community edition.
MongoDB has a dynamic schema for how data is stored in 'documents' whereas MySQL is more structured with tables, columns, and rows. MongoDB was built for high availability whereas MySQL can be a challenge when it comes to replication of the data and making everything redundant in the event of a DR or outage.
It is the least common denominator - not particularly optimized for our environment or workflows.
Hangs or slowdowns add anywhere from 5% - 7% for projects utilizing large/complicated data setts. (This could be due to other IT-imposed constraints and not entirely due to TOAD.)
Trying to perform some operations requires reading documentation and experimenting in order to figure out the TOAD-specific approaches and commands.
It just works (when we understand it). Updates don't break things and things don't suddenly start behaving differently. Best of all, we don't mysteriously lose functionality.