SQLyog-11.0.0-0.x32bit_Community (For MySql DAtabase)

SQL Yoga

SQL Yoga extends the simplicity of LiveCode to databases by allowing you to treat your database like an object. Stop wrestling with SQL and see how easy database integration can be:

Set properties rather than writing SQL
Define searches using english words rather than arcane wildcard symbols
Manipulate arrays, not cursors
Easily generate searches from complex search UIs
Tap into database table relationships to simplify code

With SQL Yoga you focus on using your data instead of worrying about accessing your data.


64 bit binaries are available from version 11.0.[5]
Editor with syntax highlighting and various automatic formatting options.
Intelligent Code Completion.
Data manipulations (INSERT, UPDATE, DELETE) may be done from a spreadsheet-like interface. Both raw table data and a result set from a query can be manipulated.
Visual Schema Designer.
Visual Query Builder.
Query Formatter.
Connectivity options: Direct client/server using MySQL API (SSL supported), HTTP/HTTPs Tunneling, SSH Tunneling.
Wizard driven Tool for import of data from ODBC-databases
Backup Tool for performing unattended backups. Backups may be compressed and optionally stored as a file-per-table as well as identified with a timestamp.
SQL Scheduler and Reporting Tool - a tool for scheduling and automating execution of any sequence of SQL statements. Result of queries may be sent as HTML-formatted reports.
Schema/Structure Synchronization and Data Synchronization.
Query Profiler and Redundant Index Finder.
All automated jobs have mail alerting and reporting options.
Full character set/Unicode support.
A Data Search[6] feature using a Google-type search syntax translated transparently for user to SQL.
Form view[7] to display one row at a time - a great way to enter/edit data.
Foreign key lookup.
Visual Data Compare.[8]

Popular Software

Warning: Unknown: write failed: Disk quota exceeded (122) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0