SQL> @ "foo.sql"
DOC>
DOC>  -- The GUID of the document i
DOC>  doc_guid varchar2(33) not null
DOC>);
DOC>
DOC>create table mx_values (
DOC>  mx_values_id varchar2(33) not null primary key,
DOC>  value_id integer not null,

The problem turned out to be caused by having newlines in my SQL commands. E.g.:

CREATE TABLE foo (
  -- The id of the foo
  id integer not null,

  -- The data of the foo
  data varchar2(200) not null
);

I did this to provide visual breaks in the code. SQL Developer was fine with it, but SQL*Plus blew up. My solution was to just make the empty lines comments using the -- comment syntax.

1/26/11 26 Jan 8:13:49 PM [0x0-0x1c61c6].com.apple.systempreferences[88942] /usr/local/mysql/support-files/mysql.server: line 256: my_print_defaults: command not found

A MySQL bug thread suggested that the server could be started directly:

sudo /usr/local/mysql/support-files/mysql.server start

however, I got the same error:

$ sudo /usr/local/mysql/support-files/mysql.server start
/usr/local/mysql/support-files/mysql.server: line 256: my_print_defaults: command not found
Starting MySQL
ERROR! Couldn't find MySQL server (./bin/mysqld_safe)

Later in that same bug thread, the actual solution can be found. The problem was a recent update to the mysql.server script. By manually specifying the install location of MySQL on mysql.server line 46:

basedir=/usr/local/mysql

the problem is resolved

$ sudo /usr/local/mysql/support-files/mysql.server start
Starting MySQL
SUCCESS!

This also corrects the problem with the preference pane.

This MSDN article shows that for modern versions of SQL Server, the following will get the full version number:

SELECT SERVERPROPERTY('productversion');

The problem with this is that it is in a string format (FYI you will need to cast it to VARCHAR), and it uses nested decimal notation (e.g. 10.0.1600.22 for SQL Server 2008). This format is very difficult to reason with, as what I am looking to do is conditionally execute SQL for SQL Server 2000 and for everything else execute some other SQL. I don’t care about minor revisions or service packs. To my knowledge, Microsoft does not provide any functions to work with nested decimals.

To make things easier, I constructed the following SQL to pull the major version number out of the string, convert it to an integer, and stick it in a variable:

DECLARE @MajorVersion int
SELECT  @MajorVersion = CAST(substring(CAST(SERVERPROPERTY('productversion') AS VARCHAR), 0, Charindex('.', CAST(SERVERPROPERTY('productversion') AS VARCHAR))) AS int);

Messy, I know. If anyone else has a better method, please leave it in the comments.