MySQL is a popular open-source relational and embedded database, now owned by Oracle.
N/A
VisualCron
Score 7.0 out of 10
N/A
VisualCron is an automation, Integration and Task Scheduler tool. VisualCron combines many features into one product. VisualCron was founded in 2004. Through scheduling users can set Jobs to run on a specific time or event with the help of Triggers. The Tasks in each Job automate scripts to eliminate human errors. Through various Tasks users can integrate different systems through file transfer, encryption, compression and…
N/A
Pricing
MySQL
VisualCron
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
MySQL
VisualCron
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
$1,499 per Server
Additional Details
—
—
More Pricing Information
Community Pulse
MySQL
VisualCron
Features
MySQL
VisualCron
Customization
Comparison of Customization features of Product A and Product B
MySQL
-
Ratings
VisualCron
3.5
1 Ratings
70% below category average
API for custom integration
00 Ratings
4.01 Ratings
Plug-ins
00 Ratings
3.01 Ratings
Reporting & Analytics
Comparison of Reporting & Analytics features of Product A and Product B
MySQL
-
Ratings
VisualCron
7.7
1 Ratings
2% below category average
Dashboards
00 Ratings
8.01 Ratings
Standard reports
00 Ratings
8.01 Ratings
Custom reports
00 Ratings
7.01 Ratings
Process Engine
Comparison of Process Engine features of Product A and Product B
MySQL
-
Ratings
VisualCron
4.2
1 Ratings
54% below category average
Process designer
00 Ratings
7.01 Ratings
Process simulation
00 Ratings
3.01 Ratings
Business rules engine
00 Ratings
2.01 Ratings
Process player
00 Ratings
8.01 Ratings
Form builder
00 Ratings
4.01 Ratings
Model execution
00 Ratings
1.01 Ratings
Business Process Automation
Comparison of Business Process Automation features of Product A and Product B
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.
VisualCron does accommodate continuous file processing. Like packing and unpacking compressed files, splitting or merging files, sending E-mail's and executing queries on databases. VisualCron in less suitable for performing very complex operations on files like, arithmetic with numbers, dates or amounts. Very complex job scripts become cluttered. Debugging Job scripts is not easy.
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.
VisualCron should more specifically indicate the root cause of an error.
If copying a file goes wrong, VisualCron reports 'can't copy file'. I expect 'no read permissions from original' or 'no write permissions from destination'.
VisualCron offers no way to execute a Job script line by line
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.
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.
Questions and problems can be addressed to VisualCron 's support department via E-mail. I usually get a good answer from them fairly quickly. There is also a VisualCron forum where you can ask questions that will be answered by other VisualCron users.
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.
For simple processes, VisualCron is easier to use and maintain. For complicated processes, Quadient Inspire offers more options. The graphical representations of waiting, running or completed jobs is adequate for both products. The logging of job actions is better in Quadient Inpire as in VisualCron.