SyBrowser: a Mac SQL client from 1999

SyBrowser was a shareware SQL client for the Mac, first released on August 17, 1999 by MacSOS Pty Ltd, the Sydney software workshop of Dr Gerard Hammond. It connected to Sybase, PostgreSQL, MySQL, SQLite, ODBC, OpenBase and FrontBase from one Mac application, and sold for about 89 USD. The domain that hosted it is still indexed today, which is why the name keeps turning up in searches for mac database software.

That single fact, a Mac SQL client shipped in 1999 and still findable in 2026, says something useful about the Mac database world. The tools change names and owners, but the job stays the same: open a connection, run a query, read the result, and do it without leaving the Mac.

What was SyBrowser for Mac?

SyBrowser was a database browser, not a database engine. It did not store data. It opened a connection to a database that was already running somewhere else, on the same Mac or on a server, and gave the user a window onto the tables, the queries and the results.

The list of supported back ends is the interesting part. Sybase, PostgreSQL, MySQL, SQLite, ODBC, OpenBase and FrontBase are not variations on one product. They are different database families with different wire protocols and different ideas about how a client should talk to them. A single Mac application that spoke to all seven was doing real work, and in 1999 that work was harder than it sounds. Mac OS 8 and 9 had no built in ODBC stack worth the name, so a client like SyBrowser had to carry its own connectivity.

Version 1.0 arrived on August 17, 1999. The price was around 89 USD, shareware, which in that era meant a download you could try before paying. MacSOS Pty Ltd ran from 1999 to about 2019 and published other Mac tools in the same period, including MacAT, a cron style scheduler, and MacODBC, a connectivity layer for classic Mac OS. SyBrowser sat between them: MacODBC made the connection possible, SyBrowser made it usable.

How do you choose a database client for Mac?

The short answer: start with the databases you actually connect to, then work backward to the client. Most people do it the other way around and end up with a tool that is excellent for one engine and useless for the other three.

Four questions settle most of the decision.

Which engines, exactly? A client that speaks PostgreSQL and MySQL covers a large share of small teams. Add SQLite and you cover local files and mobile app data. Add ODBC and you cover the long tail, including older commercial systems that never shipped a modern driver. SyBrowser's seven engine list was wide for its time, and the logic behind that width still holds: the more protocols a client speaks, the fewer clients you install.

Where does the connection live? A native driver is usually faster and simpler. An ODBC or JDBC bridge is usually more portable. If your team already maintains ODBC data sources for other software, a client that reuses them saves configuration work.

What do you do with the results? Reading a table is the easy case. Exporting a result set to CSV, charting it, or pasting it into a report is where clients separate. If your work ends in a spreadsheet, test the export path before you commit.

Who else has to use it? A client that only one person can drive is a single point of failure. Look at how the tool stores connection settings and whether a colleague can pick it up without a walkthrough.

Price matters less than it used to. SyBrowser cost about 89 USD in 1999, which was a serious purchase for an individual. Today the range runs from free and open source to subscription tools, and the free end is genuinely capable.

How do you schedule tasks on a Mac?

The classic answer is cron, and the classic Mac answer is launchd. Both run commands on a timetable without a person watching.

On macOS, launchd is the system's own scheduler. A launch agent or launch daemon is a small property list file that tells the system what to run and when. It handles intervals, calendar times and one shot jobs, and it starts jobs that were missed while the machine was asleep. For anything that has to run on a modern Mac, launchd is the default choice.

cron still exists on macOS and still works for simple repeating jobs, but it does not know about sleep, and it does not restart a job that failed. For a nightly database export, that difference matters.

This is where MacAT comes in. MacAT was a cron style scheduler for Mac server administrators, published by the same workshop as SyBrowser, with 37 tasks and a copyright range of 1999 to 2019. It belongs to the era when Mac OS X Server was finding its feet and administrators wanted a scheduler with a face, not just a text file. The category it served, run this job at this time and tell me if it failed, is the same category launchd serves now.

A practical pattern for database work: schedule the export with launchd, write the output to a dated file, and let the client handle the interactive queries. Do not schedule a GUI client to open and click. Schedule a command line tool, or a script that calls one.

What the shareware era got right

Shareware had a simple contract. Try the software, pay if you keep it, get updates. SyBrowser was sold that way at about 89 USD. MacAT was sold that way at 39 USD. Neither product had a subscription, a login server or a telemetry pipeline.

The trade off was support. A small workshop could not answer every email, and when the workshop closed, the products stopped. MacSOS Pty Ltd ran until about 2019. The domain went dark around 2022 and was bought again in 2026, now home to The Menu Bar, an Australian magazine about Mac software, the workshop side of computing, and shareware history. The old product pages, including the SyBrowser era material, are part of what that magazine documents.

For anyone choosing tools today, the shareware era offers one durable lesson: a database client is a long lived piece of software. You will use it for years, across operating system upgrades and database versions. Pick one whose data format you can read without it, and whose queries you can copy out as plain text.

The takeaway

SyBrowser is a useful marker. It shows that a Mac SQL client covering Sybase, PostgreSQL, MySQL, SQLite, ODBC, OpenBase and FrontBase existed in 1999, sold as shareware for about 89 USD, and is still indexed. The questions it raises are the questions to ask now: which engines, which connection method, which export path, and who else can use the tool.

For scheduling, use launchd on modern macOS and treat cron as a legacy option. For the client itself, test with your own data before you commit, and keep your queries in files you control.