RazorSQL

It's a good solution, but I prefer dbForge Studio for SQL Server. You can see a detailed comparison of RazorSQL, dbForge Studio, and Toad for SQL Server here: https://www.devart.com/dbforge/sql/studio/razorsql-alternative.html

Been using for a long time. Like the non traditional db support. GUI doesn't blow me away but am using it for productivity not looks.

awful software that barely functions. dont even bother.

as for the price? im still lauging.

anyone who has ever used sqlyog in windows will not tolerate such a poor piece of software. Unfortunately due to a lack of decent sql Gui's for the mac we're reduced to trying tripe like this.

RazorSQL has become one of my must-have development tools. Pros: * supports nearly every DBMS you throw at it (I've mostly used it with MySQL, SQLite, and SimpleDB) * powerful features for editing data, generating queries, import and export * developer is very responsive to bug reports and feature requests Cons: * UI takes a little getting used to * no auto-update or update-checking functionality * a bit pricy: if you don't work with multiple DBMSes or don't need advanced features, it may not be worth it.

I would give this 5 stars (which I rarely do, reserving such for truly excellent) if it had auto-update (i.e., when new versions come out). It would also be nice if it could translate one DB to another. That said, nothing else is quite like it, working equally well with such a wide variety of RDBMS. It's also rock-solid, something that PGAdmin can't claim.

This is a full-featured DB app, and it's one of the few that handles both MySQL and SQLite (among several others). I've purchased it and remain happy with it. The price is reasonable, and the publisher is constantly improving the app with frequent free updates that continue to move it forward. That said: While its appearance is far better than many "cross platform" DB solutions, it still doesn't feel like a "native" OS X app, and the overall navigation seems more cumbersome than it need be (for instance, one must open a separate "edit table" window, rather than simply editing a table in its current view). I'm sure this allows the app to be more flexible than say, the excellent Sequel Pro app for MySQL, but it also leads me to reach for those db-specific tools (such as Sequel Pro, SQLite Manager) first... which kills the point of the "one app to rule them all" that I was hoping this would provide. In other words, it DOES work well with every DB I've thrown at it -- but if you don't need to access different types of DB servers, you may find you prefer a more specialized tool designed for your particular brand of database.

Here's a detailed comparison of RazorSQL with alternative SQLite GUI programs: http://www.tandb.com.au/sqlite/compare/

The improvements look great :-) Some feedback on your feedback ;-) : 1. RazorSQL now recognizing SQLite's rowid column for updates/deletes looks great. We can edit tables now that use the rowid implicit primary key. If there is an explicit primary key, however, I think RazorSQL should default to using that key and not rowid. At present it uses both, which seems redundant (eg executes WHERE rowid = 120 AND ID = 120). And if rowid is already present in a view, RazorSQL shouldn't add yet another copy of it. 2. Tabbing through a row (from column to column) now works nicely. 3. The pop up menu option to "Edit Table" is a welcome more direct method. Perhaps better still would be for double clicking on the table/view. Double click in the entity browser currently just does the same as clicking the expansion triangle so would be better utilized. 4&6. Nulls now show as empty cells in the query results pane (great), but not in the edit window (show as "null"), which makes it look cluttered. Admittedly you'd need some way to show and enter null as distinct from empty cells when editing. Perhaps something less obtrusive than the word "null", or a reference on what to show. Presumably a text entry of the literal word "null" currently appears the same as a null, so it is currently ambiguous anyway. 5. I confirmed that RazorSQL does enter integers into an integer column in a table, thank you. It is not true that "SQLite views are read-only". SQLite uses "instead of" triggers to redirect update/insert/delete on views to tables etc, making changes to views seamless. I notice that RazorSQL thankfully still allows me to edit the data in a view if I initiate it by double clicking in the query result, but that the more direct "Edit Table" option in the pop up menu in the entity browser is disabled. Please re-enable it. As for the type of the data to be entered in an update or insert, you can use pragma table_info(tableName) to get the data types of columns in views and tables and implement it to enter the correct data type. Also, RazorSQL should enter null not '' in an insert where data cells are left empty. This is especially a problem for integer primary key columns since '' is not allowed but null is happily accepted and auto replaced by the next integer, but also unnecessarily populates '' in cells where I did not ask for anything to be entered. The incomplete support for editing views is a show stopper problem. Some more points: 7. RazorSQL shows the results of a query in a pane in the main window. When I initiate editing of data there (such as by double clicking on a data cell), RazorSQL opens a new window with a copy of that same table, and I have to locate the data cell again. It would be more intuitive, efficient and streamlined to perform the editing directly in the query result pane, rather than opening a new window. 8. Each query result shows in a new tab in the bottom right panel. They are labeled "Query 1", "Query 2" etc, which gives no indication of their origin. It would be helpful to show the table/view name. 9. The syntax coloring looks great. It would be helpful to have literals (in single quotes) show as a different color to identifiers (in double quotes). It would be even more helpful to show all identifiers (in double quotes or square brackets or unbracketed table/view/trigger/index/column names) in the same color. 10. How about a view of one record at a time, similar to "line" mode, eg: fieldname1: value of fieldname1 in record n fieldname2: value of fieldname2 in record n fieldname3: value of fieldname3 in record n fieldname4: value of fieldname5 in record n This devotes one window/screen to one record at a time, with more room to edit. 11. The SQL formatter (indenting SQL statements) is good idea, but the current implementation is of limited use, since, for instance, it treats commas in the select statement to same as commas within brackets. 12. I struggle with the Java app GUI. Native Cocoa would look and work much better. I'll review more if point 5 (editing of views) is addressed, since then I can find some use for it. Thanks.

I use this every day, mostly for Oracle, but also for MS SQL, Sybase, and Informix, and in my opinion, this is the best SQL client for the mac. I would recommend it to any developers.

RazorSQL now supports SQLite and spaces in names (of tables, views, columns etc), which is great. It seems to be unaware of the implicit rowid primary key field in SQLite, which makes editing data in some tables impossible. I like many of the features such as SQL History and the way it marks inserted, updated and deleted rows to be applied as a batch change. The editing of cells has a few problems. It shows nulls as which is a bit ugly (some sort of blank would be better). It seems impossible to enter a null since entering enters that literal string. RazorSQL doesn't seem to check the type of fields when entering values, so enters integers as text instead (at least in the tables/views I tried). Unfortunately the GUI is built on Java or something that's quite un-Mac-like and gets a bit annoying. For instance: editing the next cell in a row requires several clicks instead of just hitting tab; after selecting a table and clicking Edit, RazorSQL then asks me to re-choose the table from a pop up menu; I can't drag and drop an SQLite database file onto the app. It is one of the better SQLite editors out there, but impractical to use in every day database editing. It's improving though.

Seems like a thorough SQL database front end. But it lacks SQLite support. SQLite is built in on Mac OS X and above, and requires no server setup etc. So the user could make a database immediately using just RazorSQL, or open existing databases. Please add SQLite support.