When this question was asked there were very few tools out there were worth much. I also ended up using Fusion and a Windows client. I have tried just about everything for MAC and Linux and never found anything worthwhile. That included dbvisualizer, squirrel (particularly bad, even though the windows haters in my office swear by it), the oracle SQL developer and a bunch of others. Nothing compared to DBArtizan on Windows as far as I was concerned and I was prepared to use it with Fusion or VirtualBox. I don't use the MS product because it is only limited to MS SQL.
It works with iCloud to let you browse seamlessly across all your devices. Safari 5.1 download for mac. And it gives you great ways to find and share your favorites.
Bottom line is nothing free is worthwhile, nor were most commercial non windows products However, now (March 2010) I believe there are two serious contenders and worthwhile versions for the MAC and Linux which have a low cost associated with them. The first one is Aqua Data Studio which costs about $450 per user, which is a barely acceptable, but cheap compared to DBArtizan and others with similar functionality (but MS only). The other is RazorSQL which only costs $69 per user. Aqua data studio is good, but a resource hog and basically pretty sluggish and has non essential features such as the ER diagram tool, which is pretty bad at that. Word for mac - how to add action item check box. The Razor is lightning fast and is only a 16meg download and has everything an SQL developer needs including a TSQL editor. So the big winner is RazorSQL and for $69, well worth it and feature ridden.
Microsoft Sql Server 2016 Training
Believe me, after several years of waiting to find a cheap non windows substitute for DBartizan, I have finally found one and I have been very picky. My employer produces a simple, proof-of-concept which can be used against any ODBC data source on the web-browser host machine, through the we also produce.
These components are free, for Mac, Windows, and more. Applicable to many of the other answers here -- the Type 1 JDBC-to-ODBC Bridge that most are referring to is the one Sun built in to and bundled with the JVM. JVM/JRE/JDK documentation has always advised against using this built-in except in experimental scenarios, or when no other option exists, because this component was built as a proof-of-concept, and was never intended for production use. My employer makes an enterprise-grade JDBC-to-ODBC Bridge, available as either a or a enabling JDBC client applications in any JVM to use ODBC data sources on Mac, Windows, Linux, etc.). This solution isn't free. All of the above can be used with the ODBC Drivers for (or ) we also produce.